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

* Your Email Address
* Spam protection	Enter the letters below: .__ .___..__.. . __. [__) _/ [__]\| \|(__ [__)./__.\| \|\|/\\|.__)
Comment	>> My testing invoved several outlook versions (express, 10, 11), > >> thunderbird and three horde/imp versions on the client-side and > >> postfix, sendmail and exchange on server sides. All clients were used > >> under Windows XP - horde/imp on Firefox and IE. > >> > >> Thunderbird and the oldest horde/imp installation sent the file > >> base64-encoded and all other clients chose quoted-printable for > >> encoding the attached file. Since base64 encoding is not a problem at > >> all no server-client pair had any problems with these mails. > >> No Server had any problems at all with any of the other mails and > >> connected by outlook or thunderbird the files downloaded from that > >> mails where absolutely fine. > >> One of the three horde/imp clients had no problem either on receiving > >> the quoted-printable-attachments, but the two newer horde/imp > >> installations corrupted the quoted-printable-attachments of any mail > >> received. > >> > >> OK : Horde 2.2.5 / Imp 3.2.3 > >> > >> Error : Horde 3.0.6 / Imp H3 (4.0.4) > >> Error : Horde 3.2-cvs / Imp H3 (4.2-cvs) > > > > 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.
Attachment
Watch this ticket