[Tickets #5251] Forward multipart with qp and base64 gives incorrectly encoded MIME (sub)part in mail

[bugs at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/?id=5251
-----------------------------------------------------------------------
 Ticket             | 5251
 Created By         | horde-bugs at conuropsis.org
 Summary            | Forward multipart with qp and base64 gives incorrectly encoded MIME
                    | (sub)part in mail
 Queue              | IMP
 Version            | 4.1.3
 Type               | Bug
 State              | Unconfirmed
 Priority           | 2. Medium
 Owners             | 
-----------------------------------------------------------------------


horde-bugs at conuropsis.org (2007-04-12 09:29) wrote:

One of my users got a mail with the following MIME structure:
1 <no description>                           [multipa/Alternativ, 7bit,
9.0K]
2 &#32;&#9500;&#9472;>Message in clear text           [text/plain, quoted,
us-ascii, 4.8K]
3 &#32;&#9492;&#9472;>Message in HTML form       [text/html, base64,
iso-8859-1, 3.7K]

when he forwards it, it gives a mail with the following structure, where
the text of the forwarded message is in part 1 _and_ the whole forwarded
message is included as a MIME part:

  I     1 <no description>                       [text/plain, quoted,
iso-8859-1, 5.4K]
  I     2 <no description>                       [multipa/alternativ,
7bit, 9.0K]
  I     3 &#32;&#9500;&#9472;>Message in clear text       [text/plain,
quoted, iso-8859-1, 4.8K]
  I     4 &#32;&#9492;&#9472;>Message in HTML form   [text/html, quoted,
iso-8859-1, 3.7K]

The problem is that the contents of the subpart whose MIME headers say
"text/html, quoted, iso-8859-1" is actually base64; probably the
Content-Transfer-Encoding in the MIME header is the one of the previous
(text/plain) subpart, but it didn't actually get converted from base64 to
quoted printable. Or something like that. Actually, I find it weird that
the charset and transfer-encoding are changed at all.

Beginning of the erroneous part:

--AGENTID00131719-=_sMcQfL3yqRNdc9lqwCKbprFWr
Content-Type: text/html;
        charset=iso-8859-1
Content-Description: Message in HTML form
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

PGJvZHkgYmdjb2xvcj0iI0ZGRkZGRiI+PEI+PEZPTlQgRkFDRT0iQXJpYWwiIFNJWkU9NSBD