Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a2) Gecko/20040610 In an account that is set up to compose messages as HTML, select a message and Forward As Attachment. 1) the headers are not included in the forwarded text (used to be displayed in a table), and the "-------- Original Message --------" separator is not inluded. 2) if the message has a plain text body, that is not included in the forwarded text 2.1) if the message has an attachment, the attachment *is* included 3) if the message is multipart/related or multipart/alternative with an HTML body, that body is included 3.1) if the HTML body has an embedded image, that is included as well 4) if the message is multipart/mixed with an HTML body, the body is not inluded. Forward As Attachment works fine. Forward in plain-text mode works as expected for all messages.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040613 Firefox/0.8.0+ T-Bird: version 0.6+ (20040613) Does not appear to depend on "Forward as Attachment." Forwarding any plaintext mail leaves the composition canvas containing only my .sig RECOMEND Priority='Major'; this is a major feature. Regression since 06/09 at least

See bug 192557 comment 22 et seq.

*** Bug 248219 has been marked as a duplicate of this bug. ***

The forwarding of plain text appears to have been fixed by the updated patch to bug 192557 -- both headers and body appear correctly. Additionally, the multipart/mixed with HTML body case properly includes the body. However, any form of HTML message being forwarded omits the headers, except: a multipart/alternative, with text/plain and text/html bodies, that is displayed *As Plain*, is treated like a plain text message for inline-forwarding purposes. This part of the problem is handled by bug 250291. Resolving this as Fixed for the text/plain part.

*** Bug 246824 has been marked as a duplicate of this bug. ***