Open PaRaDoXLP opened 6 years ago
are you sure the coming email contained filename for the attachment ?
Yes, I'm sure. Example in my first message got from mail structure.
I can concur that mail sent as:
--Apple-Mail=_9F18A0EE-316B-466D-8533-55C37EF4FFB4
Content-Disposition: inline;
filename*0="This is a test to see if a super long file name is the problem a";
filename*1="ssociated with the XXXXXX mailcore2 issue that is making the fil";
filename*2="ename nil.pdf"
Content-Type: application/pdf;
x-unix-mode=0644;
name="This is a test to see if a super long file name is the problem associated with the XXXXXX mailcore2 issue that is making the filename nil.pdf"
Content-Transfer-Encoding: base64
Works as expected but:
------=_Part_285121_1474425401.1526018147237
Content-Type: application/pdf;
filename*0="This is a test to see if a super long file name is the problem a";
filename*1="ssociated with the XXXXXX mailcore2 issue that is making the fil";
filename*2="ename nil.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename*0="This is a test to see if a super long file name is the problem a";
filename*1="ssociated with the XXXXXX mailcore2 issue that is making the fil";
filename*2="ename nil.pdf"
Does not.
Where exactly the problem is located is over my head when it comes to mail syntax since these two examples are encoded slightly differently.
Do you have some updates about that question?
libetpan doesn't parse properly MIME property with continuation (0, 1, *2).
Is there a solution?
Is there a solution?
+1; more and more messages use this format now (often leaving out the plain filename=...
parameter).
Hello! Faced with such problem using MailCore2 in MacOS project.
In structure of incoming mail has attacment with name, that was separated in such way
MCOMessageParser return that attachment like in next without fileName:
Size of attachment is right, but filename was lost. Can You fix that problem?