[Tickets #1077] RESOLVED: 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
 Updated By | Michael Slusarz <slusarz at mail.curecanti.org>
 Summary    | Forwarding/replying to a base64 Content-Transfer-Encoding message
 Queue      | IMP
 Version    | 4.0.1
 State      | Resolved
 Priority   | 1. Low
 Type       | Bug
 Owners     | Michael Slusarz
-----------------------------------------------------------------------


Michael Slusarz <slusarz at mail.curecanti.org> (2005-01-26 11:13) wrote:

Yes.  I tried forwarding/replying to your message pre-patch and, as I
mentioned in a previous entry, it worked perfectly for me.  I saw no base64
text in the reply/forward text at all - it was the converted text.

Since you seem to be the only one (or one of the very few) having this
problem, I decided it really wouldn't be worth it to determine why exactly
your system was causing this strange behavior so I decided to just go ahead
and change the code.  The new code is actually a bit cleaner, less
cumbersome, and cleans up an unused function parameter and doesn't affect
performance so it is a better way of doing this anyway.