[Tickets #13835] Re: Horde breaks attachments

noreply at bugs.horde.org noreply at bugs.horde.org
Sun Feb 1 22:52:04 UTC 2015


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

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


bra at fsn.hu (2015-02-01 22:51) wrote:

When I attach an .es3 (mime type application/vnd.eszigno3, uploaded by  
the browser as application/octet-stream) file and the destination SMTP  
server supports 8BITMIME ESMTP extension, Horde encodes the attachment  
as 8bit and not as base64 as it should.
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.

If I disable 8BITMIME extension, the attachment is encoded as base64  
and is not modified at all.

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

The attached file doesn't have any long lines, but from the SMTP  
capture it can be seen that it's not base64 encoded if the 8BITMIME  
extension is announced.

I can upload long line files on request of course.



bra at fsn.hu (2015-02-01 22:51) uploaded: 1.es3

https://bugs.horde.org/h/services/download/?app=whups&actionID=download_file&file=1.es3&ticket=13835&fn=%2F1.es3





More information about the bugs mailing list