[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      | Assigned
+State      | Resolved
 Priority   | 1. Low
 Type       | Bug
 Owners     | Michael Slusarz
-----------------------------------------------------------------------


Michael Slusarz <slusarz at mail.curecanti.org> (2005-01-25 22:03) wrote:

As mentioned earlier, I still can't reproduce this (i.e. your patch doesn't
either fix nor break anything for me).  But looking at the _rebuildMessage()
code, we might as well do the decoding all the time anyway since it doesn't
really add any code and makes the code a bit simpler.  So I'll go ahead and
commit a similar solution to the one proposed here to HEAD, test it out for
awhile, and if it doesn't break anything I will commit to IMP 3.0.x.