3.43 KB, text/plain
688 bytes, text/plain
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030807 Mozilla will not display the body of a news article, on news.atkin.com, if the article contains an attachment (or other multipart MIME). Only the headers are displayed. This occurs whether or not "View->Display Attachments Inline" is selected. The entire contents of the message, including multipart MIME, *are* displayed if CTRL-U is pressed or if "View->Message Source" is selected. When I saved one of the offending articles to a local file, Mozilla exhibited the same display problem on the local copy. I will attach a copy of the offending article to this bug report after submission. Note:I originally found the problem in Netscape 7.1. Then, after "asking around", I heard from Richard Owlett <email@example.com>. He found the problem also exists in Moz 1.4 [ Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 ] and NS 4.6. Reproducible: Always Steps to Reproduce: 1. Visit the URL news://news.atkin.com:firstname.lastname@example.org OR 1. Copy the attached article to a local file. E.g., /tmp/article.eml 2. View the local article using Mozilla. E.g., file:///tmp/article.eml Actual Results: Headers for the article are displayed, but no message body (or attachment). [Type CTRL-U to see the full contents of the message.] Expected Results: Display the message body (and optionally the attachment).
Created attachment 129412 [details] Example news article that fails to display correctly This is an example of a simple text article with a simple text attachment.
The Content-type header is trashed; it should specify a boundary.
Created attachment 129494 [details] Content-Type header from the original message in the Sent folder This is a subset of the headers from the original message in my NS 7.1 "Sent" folder. Note that the Content-Type header did specify a boundary, but NS 7.1 put it on a separate line. Perhaps, the news server didn't like that and dropped the boundary line? I don't know. However, it seems that Mozilla could at least display the contents as simple text and a warning message status, if it reads a bad Content-Type header.
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.