6.0.0-beta1
9/19/25

[#5789] Forward mail wrong Content-transfer
Summary Forward mail wrong Content-transfer
Queue IMP
Queue Version 4.1.5
Type Bug
State Resolved
Priority 1. Low
Owners slusarz (at) horde (dot) org
Requester grr (at) empre (dot) es
Created 10/10/2007 (6554 days ago)
Due
Updated 10/17/2007 (6547 days ago)
Assigned 10/10/2007 (6554 days ago)
Resolved 10/17/2007 (6547 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
10/17/2007 10:45:05 PM Michael Slusarz Comment #2
State ⇒ Resolved
Reply to this comment
This works fine with HEAD.  Since forward handling has been rewritten 
for HEAD, this will be marked as resolved.
10/10/2007 11:05:06 PM Jan Schneider Assigned to Michael Slusarz
State ⇒ Assigned
 
10/10/2007 10:19:14 AM grr (at) empre (dot) es Comment #1
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Forward mail wrong Content-transfer
Queue ⇒ IMP
New Attachment: hordebug.zip Download
State ⇒ Unconfirmed
Reply to this comment
Sometimes when IMP forwards an email set a wrong Content-transfer in 
one of the parts by setting the Content-transfer-enconding to 
quoted-printable when the content is encoded in base64. I attached two 
e-mails, the original mail and the forwarded mail in the files named 
testfail and testfailfw where this bug is shown (see the last part of 
these e-mails)

Other times , IMP set the Content-transfer in a right way. I attached 
two emails, named testok and testokfw showing this behavior.

The only difference between mails testfail and testok is that testfail 
has one line  of text more than testok. Both are 
multipart/alternative,with a txt part and html part both encoded using 
base64 and utf-8 charset.


Saved Queries