Summary: | base64 TEXT/PLAIN attachment: no conversion of dos-style end of line | ||
---|---|---|---|
Product: | [Applications] kmail | Reporter: | Andreas Amann <andreas.amann> |
Component: | mime | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Andreas Amann
2003-03-06 20:38:36 UTC
is there some standard that says what pine/mutt do, is needed? Otherwise it's a wishlist. Subject: Re: base64 TEXT/PLAIN attachment: no conversion of dos-style end of line
> is there some standard that says what pine/mutt do, is needed? Otherwise
> it's a wishlist.
In rfc 2045, which to my knowledge defines Base64 encoding, we find:
6.8. Base64 Content-Transfer-Encoding
...
Care must be taken to use the proper octets for line breaks if base64
encoding is applied directly to text material that has not been
converted to canonical form. In particular, text line breaks must be
converted into CRLF sequences prior to base64 encoding. The
important thing to note is that this may be done directly by the
encoder rather than in a prior canonicalization step in some
implementations.
...
The correct behavior is therefore to convert text/plain attachments to CRLF
line breaks first, then encode in base64.
Upon receiving, we should decode from base64, and then convert the CRLF
sequences to the canonical linebreaks of the system.
so it's a bug and no wish Any way to make kmail support base64 encoding in Menu->Settings->Configure KMail->Network->Message Property ? Andreas, I believe this was fixed a while ago by David. Can you please reopen this bug report if you are still having problem with KMail 1.7 or later? Thanks. As the original reporter, I can confirm that the bug is now RESOLVED (testet with kmail 1.6.2 on "debian testing") Thanks a lot for this one! |