[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         | Michael Slusarz <slusarz at mail.curecanti.org>
 Summary            | Attachment modification (newline structure changes)
 Queue              | IMP
 Version            | HEAD
-State              | Assigned
+State              | Bogus
 Priority           | 2. Medium
 Type               | Bug
 Owners             | Michael Slusarz
-----------------------------------------------------------------------


Michael Slusarz <slusarz at mail.curecanti.org> (2006-03-07 22:25) wrote:

This one is easy enough - the quoted-printable message you provided is
broken.  The text taken directly from RFC 2045 [6.7]:

   WARNING TO IMPLEMENTORS:  If binary data is encoded in quoted-
   printable, care must be taken to encode CR and LF characters as "=0D"
   and "=0A", respectively.  In particular, a CRLF sequence in binary
   data should be encoded as "=0D=0A".  Otherwise, if CRLF were
   represented as a hard line break, it might be incorrectly decoded on
   platforms with different line break conventions.

As is plainly obvious from your message, none of the 'CR' characters are
encoded (i.e. there is no '=0D' strings in that message).  The important
part of that text is "it might be incorrectly decoded on platforms with
different line break conventions".  This is why that quoted-printable
messages may be saved /viewed correctly on some systems (e.g. a mac,
windows) but is slightly differently displayed using Horde/IMP (e.g. on
unix).  But we are doing nothing wrong in displaying the message, as we are
following the RFC (and, in fact, there is no way we could guess the correct
linebreak usage anyway).

Pursuant to your request, I have deleted your sample messages from this
ticket.