Fri, 10 Apr 2026 12:52:14 +0000 https://bugs.horde.org/ticket/1077 Forwarding/replying to a base64 Content-Transfer-Encoding message 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 Wed, 05 Jan 2005 07:56:13 +0000 https://bugs.horde.org/ticket/1077#t4173 Have upgraded IMP to v4.01 just to check whether issue was resolved in a later release. No joy - issue still exists. HTH. Wed, 05 Jan 2005 09:08:34 +0000 https://bugs.horde.org/ticket/1077#t4174 Can you upload the source of such a message? Wed, 05 Jan 2005 09:26:37 +0000 https://bugs.horde.org/ticket/1077#t4176 Due to the commercial nature of the email itself, I am unable to provide the faulting email. However, I am in the process of trying to produce a sample email which produces the result. I will upload it shortly ... sorry for the inconvenience. Wed, 05 Jan 2005 09:38:33 +0000 https://bugs.horde.org/ticket/1077#t4177 Please find attached a sample email (filename: bug-1077.txt) detailing the observed experience. HTH Thu, 06 Jan 2005 02:45:10 +0000 https://bugs.horde.org/ticket/1077#t4232 Works fine here. Michael, do you have an idea what might be happening? Thu, 06 Jan 2005 10:31:20 +0000 https://bugs.horde.org/ticket/1077#t4238 It works perfectly for me also. I have no idea why it would be doing this - and I have never seen this in 3+ years of coding. Fri, 07 Jan 2005 08:31:27 +0000 https://bugs.horde.org/ticket/1077#t4279 So where do we go from here then? Is there anything else I can provide? Would screenshots help? Fri, 07 Jan 2005 08:45:26 +0000 https://bugs.horde.org/ticket/1077#t4282 Firstly, I'm not convinced the issue reported here is correctly understood by all - I don't mean this to be an offense to anyone, just an overall feeling I getting. Secondly, please find attached a patch which *might* address the issue, we are experiencing. DISCLAIMER: As we don't know enough about the structure, logic, or coding styles which make up Horde, the intention of the submitted patch is to a) highlight the issue which plagues us, and b) hopefully point the right people in the direction to address the issue. Apply the patch at your own peril. Does this help to identify/reproduce the issue? Fri, 07 Jan 2005 10:50:43 +0000 https://bugs.horde.org/ticket/1077#t4284 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. Wed, 26 Jan 2005 06:03:42 +0000 https://bugs.horde.org/ticket/1077#t4893 Without the patch, have you tried replying to the email in bug-1077.txt? The "reply" compose window should show the problem. Likewise, the "reply to" and "forward" compose windows (see bug-1077.bmp attachment for screenshot). Thanks for your continued support with this ticket. Wed, 26 Jan 2005 18:05:10 +0000 https://bugs.horde.org/ticket/1077#t4922 Erm .. not bug-1077.bmp, see bug-1077.JPG instead. Wed, 26 Jan 2005 18:08:37 +0000 https://bugs.horde.org/ticket/1077#t4923 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. Wed, 26 Jan 2005 19:13:56 +0000 https://bugs.horde.org/ticket/1077#t4924