Mozilla Mail sending of multipart/related is not up to RFC spec (Required "Type Parameter" for the "root" body part is not generated)

NEW
Unassigned

Status

16 years ago
3 years ago

People

(Reporter: Leknor, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

16 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030319
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030319

RFC2387: http://www.rfc-editor.org/rfc/rfc2387.txt for multipart/related states
in section 3.1:

"The type parameter must be specified and its value is the MIME media type of
the "root" body part."

Sending a rich email (text/html) to myself and viewing the source you'll see a
mime part with the header:

Content-Type: multipart/related;

which is missing the type parameter.

Reproducible: Always

Steps to Reproduce:
1. Start composing a message, make sure you are in rich text mode.
2. type some text as filler
3. inside that text insert an image, from the local file system. It's important
that the image must be included in the message insteead of externally referenced.
4: Send the message to yourself
5: View the source and find any "Content-Type: multipart/related;" lines. The
type paramter will be missing.

Actual Results:  
I got a message with an improperly formed multipart/related mime part.

Expected Results:  
Added the type parameter to the multipart/related Content-Type as per rfc.

On line 36 of the message linked in the url field is the invalid
multipart/related header.
(Reporter)

Comment 1

16 years ago
Created attachment 119240 [details]
Example email with the problem mime part header

Check line 36
(Reporter)

Updated

16 years ago
Keywords: mail6

Comment 2

16 years ago
I am experiencing this problem as well. This affects message viewing in
squirrelmail. the Plaintext part is the only part shown, as squirrelmail can't
determine the related part is text/html. Current workaround is to send as html
only (options -> format -> rich text (html) only).

-Josh
Although I don't like to code workarounds for non RFC compliant mail I just 
added a workaround to the SquirrelMail source (1.4.2 CVS and 1.5 CVS) so this 
Mozilla bug does not influent the displaying of multipart/related attachments 
anymore inside SquirrelMail. 
Product: MailNews → Core

Updated

13 years ago
Assignee: ducarroz → nobody
OS: Linux → All
QA Contact: stephend
Hardware: PC → All

Updated

11 years ago
QA Contact: mime
(Assignee)

Updated

11 years ago
Product: Core → MailNews Core
Summary: Mozilla Mail sending of multipart/related is not up to RFC spec → Mozilla Mail sending of multipart/related is not up to RFC spec (Required "Type Parameter" for the "root" body part is not specified)
Summary: Mozilla Mail sending of multipart/related is not up to RFC spec (Required "Type Parameter" for the "root" body part is not specified) → Mozilla Mail sending of multipart/related is not up to RFC spec (Required "Type Parameter" for the "root" body part is not generated)
William this might have been fixed by bug 351224. Could you take a few minutes and download the latest nightly ( http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-comm-central/ ), backup your profile and test and let us know if this is fixed or not ?
Removing myslef on all the bugs I'm cced on. Please NI me if you need something on MailNews Core bugs from me.
You need to log in before you can comment on or make changes to this bug.