User-Agent: Mozilla/5.0 (X11; U; Linux i686; pl-PL; rv:1.5b) Gecko/20030827 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; pl-PL; rv:1.5b) Gecko/20030827 "Edit as new" does not work, if you want to edit an attachment of the message, which is a message itself (the entry in the menu is accessible). Reproducible: Always Steps to Reproduce: 1. Forwards a message as an attachment to yourself (or send a message to a non existing mail address to receive an error notification with original message attached) 2. Open the message (after it arrives) 3. Open the attachment (which is another message) 4. Right-click on the body of the message and select "Edit as new..." Actual Results: Nothing happens Expected Results: The new message composition with message content should pop up This may be a dup of bug 149666, but the description there is so bad that I can't figure out if we are speaking of the same thing. Note that "Edit as new" is particularly useful for sending again messages which were returned with an error. It would be nice to make it work (or make mozilla support resending this messages more explicitly).

149666 isn't related. This bug may be a dupe of bug 2920 by way of bug 121728. Or possibly bug 91515...

Ooops! I did meant that it might be a dup of bug 91515. Must have copeied&pasted th id from the wrong bug. It is bug 91515, that I can't understand if it is saying the same thing or not.

i believe it's none of those.

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

When Edit-as-New is attempted on the attachment (in a standalone message window), the JavaScript console dumps this error: Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgMessageService.messageURIToMsgHdr]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome: //messenger/content/mailCommands.js :: ComposeMessage :: line 215" data: no] Also note: Edit as New under the window's Message menu is disabled; it's only enabled via the context menu on the body. See also bug 231282.

Add "message/rfc822" in summary for ease of search.

This bug has been fixed by the patch to bug 204350.