[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         | Michael Slusarz <slusarz at mail.curecanti.org>
 Summary            | "forward" handles text/alternative wrongly
 Queue              | IMP
 Version            | 4.0.3
 State              | Assigned
-Priority           | 2. Medium
+Priority           | 3. High
 Type               | Enhancement
 Owners             | Michael Slusarz
-----------------------------------------------------------------------


Michael Slusarz <slusarz at mail.curecanti.org> (2006-02-02 17:54) wrote:

Damn - I just wrote a page for this ticket and my session timed out :(

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.

This will just be in HEAD for awhile but if the reaction is good there, this
should probably be backported before we release 4.1.0.