Hello again, seems like I'll be debugging all day long :/
In my test scenario I use a GMail account, I've sent a ZIP file to that address, and tried to retrieve it with ImapX. The file constantly got corrupted.
When I debugged, I noticed that the last line of the received base64 data was ended with the BODY....etc. ending marker (I guess, I'm not good at e-mail protocol). When the code replaced this marker (MimeRex), it deleted also the last portion of the base64 data, because the Regex looks like this:
.*BODY\[[\d\.]+MIME\] \{\d+\}
I replaced it with this (to let any beginning until an equation mark):
[^\=]*BODY\[[\d\.]+MIME\] \{\d+\}
and now everything works well. Please examine the scenario in depth, possibliy this will cause other unwanted side-effects. But fo now I'm happy that I can process the attachments.
I've downloaded the latest code this afternoon, I found this issue there. But with the official release it was corrupted as well, so I guess it's not a new one.
Thank you,
Zoltán
In my test scenario I use a GMail account, I've sent a ZIP file to that address, and tried to retrieve it with ImapX. The file constantly got corrupted.
When I debugged, I noticed that the last line of the received base64 data was ended with the BODY....etc. ending marker (I guess, I'm not good at e-mail protocol). When the code replaced this marker (MimeRex), it deleted also the last portion of the base64 data, because the Regex looks like this:
.*BODY\[[\d\.]+MIME\] \{\d+\}
I replaced it with this (to let any beginning until an equation mark):
[^\=]*BODY\[[\d\.]+MIME\] \{\d+\}
and now everything works well. Please examine the scenario in depth, possibliy this will cause other unwanted side-effects. But fo now I'm happy that I can process the attachments.
I've downloaded the latest code this afternoon, I found this issue there. But with the official release it was corrupted as well, so I guess it's not a new one.
Thank you,
Zoltán