Consider a message, for example a bounce message, which has an imbedded message/rfc822. The user can click on the paperclip button, then double-click on the imbedded message/rfc822 to display the imbedded message. Unfortunately, the imbedded message cannot be forwarded. There should be some way to forward the imbedded message/rfc822, as if it were a top-level message.

Being able to do most of the other operations on the "Message" menu make sense. Reply, Edit as new, Copy, and Add to Addressbook. Move, Mark, and the Thread items would not make sense.

Hmm. Maybe a libmime issue? -> rhp

I'll put this on the list...could be a libmime issue, but I will have to investigate. - rhp

Won't get here before M5.

Enhancements will probably be later in the cycle.

Pushing enhancements out past B1. - rhp

I don't think this needs to be fixed for PR1

Moving to the helpwanted list

Moving target milestone to "future" to be reviewed at a later time

Changing qa assigned to myself.

Change QA from pmock to fenella

To Esther...

See also bug 69359.

Do we seriously have to detach attachments from the incoming message and manually attach them to a forwarded message to include attachments in the forwarded message?? This is way annoying. Since we are nearing 1.0 can the importance of this "enhancement" be reconsidered?

Duplicate or related bugs: bug 3901 bug 11013 bug 34150 bug 55344 bug 69359

This has been fixed by the patch for bug 204350.

(In reply to comment #16) > This has been fixed by the patch for bug 204350. If this is fully fixed by 204350, then shouldn't bug 34150 be removed as blocker? Also, does Bug 11013 factor in?

(In reply to comment #17) > (In reply to comment #16) > > This has been fixed by the patch for bug 204350. > > If this is fully fixed by 204350, then shouldn't bug 34150 be removed as > blocker? Yep. > Also, does Bug 11013 factor in? No, that's unrelated.