User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030104 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030104 If I receive pdf files from people on Macs, the pdf file is not seen, just the resource fork for them. But if message is saved and then opened in Outlook, then file(s) are viewable [Both files and Resource forks]. If they Stuff the file first, the problem does not exist. So far it only seems PDF's are problematic. Or if I go ahead and save the file first and then double click and open it, then that work fine. (NOTE Name seems to pick up the resource fork name. It has the % appended to the beginning.) NOTE: <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=185230">Bug 185230 - Corrupted PDF files arriving at recipiants email.</a> Is similar, but different in that files I SENT from a Windows NT4 machine were corrupted when they arrive. Reproducible: Sometimes Steps to Reproduce: 1. Have someone on a mac attach a DPF file to an email 2. email it to you on a windows machine 3. You SHOULD see <B>two</b> files <SAMPLE> test.pdf %test.pdf </sample> Actual Results: But what I've seen was just the %test.pdf file. And when I attempt to open it, it says it's not a pdf file. But if I save it, and then double click that file. I CAN open it. Expected Results: You should be able to open up the file the first attempt.

confimed on 20031003 The MIME structure looks something like this: Content-Transfer-Encoding: base64 Content-Type: application/applefile; name="%FewerLeon.pdf" Content-Disposition: attachment; filename="%FewerLeon.pdf" ; modification-date="Wed, 15 Jan 2003 13:24:02 -0800" AAAAAAAFuB1wBbgdckttDAAFuCHN --============_-1169455540==_D============ Content-Type: application/pdf; name="FewerLeon.pdf" ; x-mac-type="50444620" ; x-mac-creator="4341524F" Content-Disposition: attachment; filename="FewerLeon.pdf" Content-Transfer-Encoding: base64 JSVFT0YN --============_-1169455540==_D============--

*** Bug 185230 has been marked as a duplicate of this bug. ***

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