[Tickets #1077] NEW: Forwarding/replying to a base64 Content-Transfer-Encoding message

[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=1077
-----------------------------------------------------------------------
 Ticket     | 1077
 Created By | clawrence at optimiser.com
 Summary    | Forwarding/replying to a base64 Content-Transfer-Encoding message
 Queue      | IMP
 Version    | 4.0-RC3
 State      | Unconfirmed
 Priority   | 2. Medium
 Type       | Bug
 Owners     | 
-----------------------------------------------------------------------


clawrence at optimiser.com (2005-01-04 23:56) wrote:

The situation:

Received a base64 content transfer encoded email message.  Viewing the
message correctly decodes the email body.  Replying to the message, does not
decode the received body - just quotes the original base64 encoded email
body.  Likewise, a similar outcome is observed when forwarding the received
message.

Here are some of the headers of the received message:

Subject: RE: E-Learning Showcase - Market Report & Feedback
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64
content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Wed, 29 Dec 2004 11:20:17 +0800