Attachment of malformed messages not included when forwarded inline (multipart/related vs. multipart/mixed)
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
People
(Reporter: ashurr_83, Unassigned)
References
Details
(Keywords: testcase-wanted)
Attachments
(1 file)
|
258.98 KB,
image/jpeg
|
Details |
Comment 1•14 years ago
|
||
Comment 4•14 years ago
|
||
Comment 6•14 years ago
|
||
Updated•14 years ago
|
Updated•14 years ago
|
Updated•13 years ago
|
Updated•13 years ago
|
Comment 8•7 years ago
|
||
I was confronted with this problem this week. I found this entry and blamed Outlook. Then I tried to find why M$ would not solve this. Well, it appears there are two guidelines (please find excerpts below) and guess what: it's ThunderBird that seems to be non compliant.
I actually experimented with the incoming mail from Outlook and changed related to mixed. The attachment was now kept in the forwarded mail.
Please reconsider to make this change in Thunderbird.
https://www.rfc-editor.org/rfc/rfc2049.txt
RFC 2049 MIME Conformance November 1996Multipart:
-- Recognize the mixed subtype. Display all relevant information on the message level and the body part header level and then display or offer to display each of the body parts individually.
-- Recognize the "alternative" subtype, and avoid showing the user redundant parts of multipart/alternative mail.
-- Recognize the "multipart/digest" subtype, specifically using "message/rfc822" rather than "text/plain" as the default media type for body parts inside "multipart/digest" entities.
-- Treat any unrecognized subtypes as if they were "mixed".
https://www.rfc-editor.org/rfc/rfc2387.txt
RFC 2387 Multipart/Related August 1998
The Multipart/Related content-type provides a common mechanism for representing objects that are aggregates of related MIME body parts.User agents that do not recognize Multipart/Related shall, in accordance with [MIME], treat the entire entity as Multipart/Mixed.
Comment 9•7 years ago
|
||
(In reply to Fred_Dingelhoff from comment #8)
I was confronted with this problem this week. I found this entry and blamed Outlook. Then I tried to find why M$ would not solve this. Well, it appears there are two guidelines (please find excerpts below) and guess what: it's ThunderBird that seems to be non compliant.
I don't think that's how these should be interpreted. Thunderbird does recognize multipart/related, so neither of the quoted RFC passages apply. Those would only matter if we had no multipart/related handling at all. In fact, RFC2387 is pretty clear that multipart/related isn't a good place to put a regular attachment: "For a Multipart/Related object, proper display cannot be achieved by individually displaying the constituent body parts."
That doesn't mean the Thunderbird team shouldn't fix the bug (that's why it's not WONTFIX), but it's not an RFC violation.
Comment 10•7 years ago
|
||
Thank you for your reply. You are right (of course) that Thunderbird does display the message from Outlook and offers the attachment to open (although the size is not available!).
I found a link to https://support.mozilla.org/nl/questions/1176526 where multipart/related is used in Thunderbird and I think I now understand better how it was meant to be used.
Still leaves me with the test where I manually changed the incoming mail from Outlook to use multipart/mixed (simulating what was suggested in RFC 2049). This resulted in a correctly mentioned size and a correctly forwarded mail...
Updated•4 years ago
|
Comment 11•7 months ago
|
||
I don't see a .eml here (or exact headers for that matter) to reproduce, but I am positive that this is fixed in the current state of https://phabricator.services.mozilla.com/D292070 for bug 2029333.
Comment 12•3 months ago
|
||
WFM per comment 11
Description
•