User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3a) Gecko/20021114 Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3a) Gecko/20021114 I've gotten a number of complaints that PDF files (Just PDF's) were corrupted when received. ZIpped files come out ok and finally I had one person forward the file back to me and I noticed some **** when opened up in a text editor (note bottom after %EOF). Reproducible: Always Steps to Reproduce: 1. Address email 2. Attach PDF file directly (note I have an JPG as part of signature. Also these email end with telling me that they can't be saved in sent folder.) 3. Recieve file. Actual Results: Everything looks fine except that you get an error abut a corrupted file from Acrbat and if you look at the guts, it's not correct. Expected Results: It seems the MIME parsing is off... Plus I've gotten two SERVER messages about the headers being too long after these emails. I'll be adding the eml file for the Server messages... plus the forwarded back pdf file. Contact for more info.

The eml file was too large to attach, so I just put it up on our server. http://mmp-napa.dnsalias.com/~phavens/message.eml

Is the PDF file that you attached as http://bugzilla.mozilla.org/attachment.cgi?id=109237&action=view the corrupted one you tried to view/save from the email, or is it the original? I can't even view that in the stand-alone Acrobat viewer I have, if it's the original. Also, when I move your email to Local Folders and try to view it, nothing shows up, so I can't test anything about that email, yet. I'll keep trying, perhaps something is off with the headers.

From Phil, via email (in the future, please comment directly in Bugzilla, thanks) The PDF file is the one forwarded back to me from one of the people who got "corrupted" files. I have saved the email and placed it on my server as message1.eml and message2.eml. The first is a bounce back (problems with headers) and the second is the actual email. http://mmp-napa.dnsalias.com/~phavens/

Aha! The PDF file is sent AppleDouble-encoded. I think we have a few outstanding bugs with this encoding, I'll check.

See also bug 142517.

Patrick Havens, your server currently has three .eml files up: message.eml message2.eml message3.eml How do these files correspond to the information in comment 4? If the Apple DoubleCoding is in fact a problem, bug 189248 has a similar issue -- the attachment to that bug shows the PDF part is wrapped in Content-Type: application/applefile

message.eml was the first message. message2.eml was the maessage forwarded back to me from a customer. message3.eml was a message from another customer. NOTE: I have only rarely been getting these issues now. Don't know if it's because currently I'm running a nightly. Or whether it's because I stopped sending PDF files via email pretty much. (or I zip it first) Not sure why it's only PDF's that have this issue. And I'm on a PC they are on a Mac EXCEPT the second email where we both are on PC... Where does the appledouble coming into that situation?

*** This bug has been marked as a duplicate of 189248 ***