6.0.0-beta1
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
7/26/25
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#3565] Attachment modification (newline structure changes)
*
Your Email Address
*
Spam protection
Enter the letters below:
.__.. ..__ .__ __. | || |[ __[ __(__ |__\|__|[_./[_./.__)
Comment
> It sounds like you are still not understanding the issue. What the > RFC essentially says is that Quoted-Printable (by default) is not > able to reliably handle binary data. This is because the Q-P > algorithim differs depending on whether you are feeding it binary vs. > non-binary (e.g. text) data. Namely, the encoding of line ending > characters differ depending on whether the data is binary or not. > > > > What is important for our purposes is that there is absolutely no way > to determine whether a given data stream is binary or not if it > contains only 7bit characters. The only way to tell if data is > binary is via outside information. If IMP determines the data is > binary, we encode in base64. If it is text we encode in > quoted-printable. > > > > In this case, IMP is determining the binary-ness of the data via the > mime type the browser is reporting when uploading the file (or via a > MIME magic call if the data is uploaded via > application/octet-stream). In your case, the browser is reporting > this data as a text/* part. By definition of the RFCs, a text/* part > is NOT BINARY DATA. Thus, we are encoding the file correctly. The > issue is with either with your browser or the mime magic regexs. In > either case, there is nothing broken with the way Horde/IMP is > encoding/decoding the data.
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