6.0.0-beta1
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
11/8/25
H
istory
A
ttachments
C
omment
W
atch
Download
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
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers