Tickets :: Comment on [#3381] "forward" handles multipart/alternative incorrectly

* Your Email Address
* Spam protection	Enter the letters below: .__..___. . ,.___. \| \|[__ \| \./ _/ \|__\[___\|___ \| ./__.
Comment	>> Quick synopsis then: I have been wrestling with this issue for way > >> too long now and finally have decided to at least try forwarding > >> always as a message/rfc822 part instead of trying to be fancy in > >> figuring out what parts should be forwarded. I have implemented > >> (sort of) #2 with the addition that we still put the text of the > >> first viewable text part into the message body window. This is > >> because I (at the least) find it very useful when forwarding messages > >> to others in order to point out details of the forwarded message for > >> example. But since the original text part is in the rfc822 part, the > >> concerns raised below about differing text is alleviated. > > > > I'm not really in favor of this. For one thing, wasn't whether or not > to forward as attachment a preference before? I also like having the > ability to pick and choose which attachments get forwarded when I > forward a message. > > > > Seems to me like we should be able to, if forwarding a > multipart/alternative message inline, just not add as attachments any > other alternatives to that part. Is it not that simple?
Attachment
Watch this ticket