[Tickets #13835] Re: Horde breaks attachments

[noreply at bugs.horde.org]

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

Ticket URL: https://bugs.horde.org/ticket/13835
------------------------------------------------------------------------------
  Ticket             | 13835
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Horde breaks attachments
  Queue              | Horde Framework Packages
  Type               | Bug
  State              | Unconfirmed
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2015-02-02 19:15) wrote:

> This means the attachment will be converted to CRLF line endings and  
> a CRLF will be inserted after 998 characters by the SMTP server if a  
> line is longer than that, therefore breaking the XML parser on the  
> receiver end and breaking any checksum validations.

You are incorrect.  http://www.w3.org/TR/REC-xml/#sec-line-ends

When normalized as is required, the data is EXACTLY the same as when sent.

> AFAIK, Horde should base64 encode any non text/* mime types.

False.  Directly from the MIME RFC:

"It may seem that the Content-Transfer-Encoding could be
inferred from the characteristics of the media that is to be encoded,
or, at the very least, that certain Content-Transfer-Encodings could
be mandated for use with specific media types.  There are several
reasons why this is not the case."