User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020818 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020818 When an email is attached to a message, and view that message in mozilla mail, it displays the email inline. However, the Content-Type header incorrectly displays the content-type of the main email you are viewing, instead of the content type of the attached email. If you view the message source, you will see the correct content-type. However, if you copy the email from the inline view, you will end up losing the data that describes the content type of the attached email. I will submit two attachments showing the problem. Reproducible: Always Steps to Reproduce: 1. Send yourself an email with an attached plaintext email message. 2. View this email in mozilla mail. 3. Notice the content-type of your attached message is shown as a multipart, even though it was plaintext. 4. View message source to confirm inaccuracy.

This screenshot shows the incorrect Content-Type that is being displayed for an email attachment being shown inline (circled in red). The content type shown is actually that of the main email message that includes this attachment. I have blacked out some areas to protect our network identities.

This is a screenshot of the email being shown in a separate window, done by double-clicking on the attachment. You can see the content-type (circled in red) is correctly shown as text/plain. I have blacked out some areas to protect our network identities.

viewed inline, attachment shows content-type: multipart/mixed; boundary="------------020104010909090203040304" Viewed separately, attachment shows content-type: text/plain; charset=us-ascii; format=flowed Please verify if this is a bug

By the definitions on <http://bugzilla.mozilla.org/bug_status.html#severity> and <http://bugzilla.mozilla.org/enter_bug.cgi?format=guided>, crashing and dataloss bugs are of critical or possibly higher severity. Only changing open bugs to minimize unnecessary spam. Keywords to trigger this would be crash, topcrash, topcrash+, zt4newcrash, dataloss.

Note that the bug to which this is duped has been fixed. Also, comment 4 is correct: this bug should not have been given 'critical' severity. *** This bug has been marked as a duplicate of 140532 ***

Verified dup.