[Tickets #3381] "forward" handles text/alternative wrongly

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=3381
-----------------------------------------------------------------------
 Ticket             | 3381
 Updated By         | Chuck Hagenbuch <chuck at horde.org>
 Summary            | "forward" handles text/alternative wrongly
 Queue              | IMP
 Version            | 4.0.3
 State              | Assigned
 Priority           | 3. High
 Type               | Enhancement
 Owners             | Michael Slusarz
-----------------------------------------------------------------------


Chuck Hagenbuch <chuck at horde.org> (2006-02-05 09:53) wrote:

> 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?