Tickets :: Comment on [#13835] Horde breaks attachments

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