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

* Your Email Address
* Spam protection	Enter the letters below: . ..___..__..___..__ \|\/\| _/ [__] \| [__) \| \|./__.\| \| \| \|
Comment	>> 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?
Attachment
Watch this ticket