Closed Bug 213712 Opened 22 years ago Closed 21 years ago

Named message body of multipart messages not displayed

Categories

(MailNews Core :: MIME, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: patrick, Assigned: sspitzer)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030626 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030626 The body of a mime/multipart message is not displayed if "display attachments inline" is disabled and the content-type contains a name field like in the following example. There is no attachment with that message part eiter. This is eg. a problem for inline-PGP encrypted multipart mails from KMail 1.5. Reproducible: Always Steps to Reproduce: sample mail: From: xxx@domain.invalid To: yyy@domain.invalid Subject: Test Mail MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_Nq9H/wVvCfvkU9l" --Boundary-00=_Nq9H/wVvCfvkU9l Content-Type: text/plain; charset="us-ascii"; name="this is a test" Content-Transfer-Encoding: 7bit this is a test message --Boundary-00=_Nq9H/wVvCfvkU9l Content-Type: application/pgp-encrypted; name="wt_mkt_bro_copro.pdf.pgp" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="test.txt.pgp" hQQOA+mvfTmHW5pMEA/+MLmpM9GuU/ZnJbaO6aMDz029hhI1spJyOWPdWaqkYSWOhVLEdK6Y2KnP 1qGC2M054ucSEMfRIFDsafeos/xi4Ai33hRxoK2b0joH6WO0SFqetjQgGg5O5keWdXKiUiZb/hGm iRLhRzLjBQ/Z8FXfvA2+8fWY+fF3St1xrlxqhdJMNia1Of4oItHBcu/T2xW4wMqCCQxLoZ0nrT+t pNOYaEiOTwlwfpk95RdTjnEVanf8aOpzqrryROntHrPNCRrHrDXn4CjpPsMCdYbEemuSmaLXgSeZ b5kfndHXzWRXwyfG3CAVyG4wQ34sf8AQkqJOaoCGxF3f2wMqpdaQ/+A19kgCs8YEZPq6cxvFVX9v D4BWZ3sOLl31ts/mBjvJ7Wptpg2R9bCFbjkNKDX931F8mSo83hNfw+B9mNfN5Rgmkr3bMmC3xkcO qSuP2Yi8XcvbNtLoP/B0KfimIgLFiaYLz/5mBgiI+3u1x35TWaljEO9bT8QaCiClIpW1JWWHGHC4 mvGYk4dNp0Vd/gqhcNdIalRhRpinYlo1ZrTVe6GYWODmAc1mgOa55JNjsck= --Boundary-00=_Nq9H/wVvCfvkU9l--
Patrick Brunschwig, is this bug still a problem for you? I integrated your sample into my mail, and I am seeing the file name "test.txt.pgp" displayed in the attachment panel. Moz 1.7b-0406, Win2K.
Yes, the problem is still there. Instead of the mime part being passed properly to the content-type handler (Enigmail in this case, but it's the same for S/MIME messages), the mime part is displayed as attachment. The point is that this only happens if there is a "name" field in the first mime part like the name="this is a test" example. And actually, it's not a problem of mails I receive personally, I just happen to be the author of Enigmail :-)
OK, I see; I misread the bug earlier. I can easily see this part (comment 0): > The body of a mime/multipart message is not displayed if "display attachments > inline" is disabled and the content-type contains a name field So I'm confirming; reproduced this with Moz 1.6 and Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040406 I'm not sure about this part (comment 2): > Instead of the mime part being passed properly to the content-type handler > (Enigmail in this case, but it's the same for S/MIME messages), the mime part > is displayed as attachment. That sounds like a different issue. By "the mime part" you mean the "application/pgp-encrypted" part from your sample? (Which is tagged with "content-disposition:attachment".) Should that part be automatically passed to a handler? If we have, for instance, an "application/pdf" attachment, Mail/News doesn't automatically launch Acrobat. Of course, that's with a plug-in; I don't know how Enigmail integrates at this level.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: PC → All
I'm sorry, just realize that I made a mistake! The message is an inline PGP message, so that there is nothing to do if the Content-Disposition is "attachment". I thought I was talking about PGP/MIME and S/MIME.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
OK, we'll leave it Invalid; but I just realized that the original symptom described in comment 0 is bug 182627.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.