[Tickets #3565] RESOLVED: 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
 Updated By         | ag at netside.de
 Summary            | Attachment modification (newline structure changes)
 Queue              | IMP
 Version            | HEAD
 State              | Bogus
 Priority           | 2. Medium
 Type               | Bug
 Owners             | Michael Slusarz
-----------------------------------------------------------------------


ag at netside.de (2006-03-28 23:31) wrote:

> This is exactly what is expected (and what the RFC is warning about). 
>  Namely that different MUAs can decode the file correctly and yet get 
> different results.

Different results depending on their OS ... i tested Thunderbird on Linux
and Windows with these files and compared the results. On Linux the
downloaded attachment had Unix-style linebreaks and on Windows it had
Windows-style linebreaks. Yes the resulting files differ, but that is what i
expected and what i was wondering if horde/imp should do the same. If
someone reads his/her mail from a linux-browser these kind of attachments
are ok if saved and viewed with a linux editor and if someone reads his/her
mail from a windows-browser these kind of attachments have unix-style
linebreaks and are not quite readable with a cheap editor that doesn't
recognize these linebreaks.

Its a fact that quoted-printable doesn't (need to) encode linebreaks on
text-files. Thus these linebreaks transform into unix-style linebreaks on
mail transport. Why not let the decoder of quoted-printable text-files
substitute linebreaks to the linebreak-style of the browsers-os?