Summary | Forwarding/replying to a base64 Content-Transfer-Encoding message |
Queue | IMP |
Queue Version | 4.0.1 |
Type | Bug |
State | Resolved |
Priority | 1. Low |
Owners | slusarz (at) horde (dot) org |
Requester | clawrence (at) optimiser (dot) com |
Created | 01/05/2005 (7489 days ago) |
Due | |
Updated | 01/26/2005 (7468 days ago) |
Assigned | 01/06/2005 (7488 days ago) |
Resolved | 01/26/2005 (7468 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
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.
New Attachment: bug-1077.JPG
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.
State ⇒ Resolved
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.
New Attachment: imp-message-decode.diff
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?
Is there anything else I can provide?
Would screenshots help?
Priority ⇒ 1. Low
this - and I have never seen this in 3+ years of coding.
Assigned to Michael Slusarz
State ⇒ Assigned
New Attachment: bug-1077.txt
the observed experience.
HTH
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.
State ⇒ Feedback
Version ⇒ 4.0.1
a later release. No joy - issue still exists.
HTH.
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Forwarding/replying to a base64 Content-Transfer-Encoding message
Queue ⇒ IMP
State ⇒ Unconfirmed
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