User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6a) Gecko/20031030 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6a) Gecko/20031030 Received a joke e-mail from someone using Outlook. It contained an inline image but this image wasn't displayed in Mozilla. It was displayed in my copy of Outlook Express. Reproducible: Always Steps to Reproduce: 1. Make sure View > Message Body As > Original HTML is selected. 2. Copy the first attachment to a Mozilla Mail folder (e.g. Inbox). 3. Restart Mozilla if necessary. 4. Show the mail. Actual Results: The mail was displayed but with the 'broken image' icon in place of the inline image. Expected Results: The inline image should have displayed. This is to do with the Content-Location line. It's split over two lines and the split is interpreted differently between Outlook/Outlook Express and Mozilla. First attachment has a newline and tab character half-way through the name... Content-Location: ATT-0-B4E54243706B2244A2D501BF42A394E6-i mage001.gif Second attachment has the split removed... Content-Location: ATT-0-B4E54243706B2244A2D501BF42A394E6-image001.gif If you redo the steps using the second attachment (which is the first with the split removed) the message displays correctly in Outlook Express and Mozilla.

Spaces and Blanks in an URI? For me Chapter 4.1 of RFC 2557 doesn't look like that's allowed: content-location = "Content-Location:" [CFWS] URI [CFWS] URI = absoluteURI | relativeURI where URI is restricted to the syntax for URLs as defined in Uniform Resource Locators [URL] until IETF specifies other kinds of URIs.

True, but as Outlook and OE are so widely used it might be better to be pragmatic in this case ("be liberal in what you receive and conservative in what you send").

I think that when a header is folded, only the newline character is removed during the unfolding. If you create a message with: Subject: Here is a broken subj ect line When you display that message, it shows up as Subject: Here is a broken subj ect line This behavior also causes problems when a fold takes place within the 'boundary' parameter of a Content-Type header -- see bug 234547 comment 9. The problem is, if Mozilla removes *all* the whitespace, it's as prone to error as if Mozilla makes some educated guess about how much whitespace to leave -- those boundary separators from Yahoo apparently *intentionally* include whitespace.

Would treating tabs differently to spaces when folding help? It looks like OE splits the filename over two lines with a newline, a single tab, and the rest of the filename. So by folding the two lines together deleting the single tab character would perhaps be the same way that OE interprets header lines. This wouldn't fix subject lines or the Yahoo boundry ID problem though. Subject lines would probably be better folded by folding spaces at the end of the first line and the start of second line into a single space.

This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/

This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.