[Tickets #3565] NEW: Attachment modification (newline structure changes)

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=3565
-----------------------------------------------------------------------
 Ticket             | 3565
 Created By         | ag at netside.de
 Summary            | Attachment modification (newline structure changes)
 Queue              | IMP
 Version            | HEAD
 State              | Unconfirmed
 Priority           | 2. Medium
 Type               | Bug
 Owners             | 
+New Attachment     | mail-examples.zip
-----------------------------------------------------------------------


ag at netside.de (2006-03-06 03:51) wrote:

Notice: imp/test.php says version H3 (4.2-cvs)

Scenario: An automated ordering system is receiving email-orders with
defined orderfiles from customers. All customers use a offline ordering
software that generates the orderfile which then has to be (manually) sent
to the adress of the ordering system.

I got complains about modified orderfiles from certain customers after
switching the mailserver over to horde/imp. So i took a closer look at those
emails since not all order-emails had corrupted attachments. It clearly
depends on the sender of the email - or to be more specific: the mailer used
to send the email seems to be the factor.

I grabbed two example orders from that queue (see attached zip)

What happens: The attachment is a textfile with 0x0d 0x0a as
newline-sequence. Saving the attachment and examining it reveals no change
if the attachment was base64 encoded. If the mailer had put this attachment
as quoted-printable these newline-sequences are changed into 0x0a 0x0a.

To verify the source of the problem i asked one of these
"quoted-printable"-senders to send to my private account (no horde/imp -
sorry). I found no changes on the saved attachment. So the sending mailer
does not change the attachments newline-sequence but certainly horde/imp
seems to.

Im pretty sure "quoted-printable" is the source for this problem, but maybe
its a good idea to change imps behavior when an attachment is marked as
"Content-type: application/octet-stream"