[exim-dev] [Bug 638] rfc2047 encoding doesn't work correctly

Αρχική Σελίδα
Delete this message
Reply to this message
Συντάκτης: Kjetil Torgrim Homme
Ημερομηνία:  
Προς: exim-dev
Παλιά Θέματα: [exim-dev] [Bug 638] New: rfc2047 encoding doesn't work correctly
Αντικείμενο: [exim-dev] [Bug 638] rfc2047 encoding doesn't work correctly
------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=638

Kjetil Torgrim Homme <kjetilho@???> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |LATER





--- Comment #4 from Kjetil Torgrim Homme <kjetilho@???> 2008-10-24 01:42:35 ---
apologies for being a pedant, but Exim follows RFC 2047 to the letter. RFC
2047 says that the length of an encoded word can not surpass 76 letters, but it
says nothing about the length of lines. this is left to RFC 2822 and 2821 (now
RFC 5322 and 5321 although I don't think anything has changed). 2821/5321
restricts the length of a line to 1000 octets, while 2822/5322 says SHOULD NOT
exceed 78 characters (excluding CRLF) in header fields.

anyway -- in a hypothetical Exim 5, I would like to see it use CRLF internally,
and functions like rfc2047 should separate word with CRLF SP. but for Exim 4,
I think it's best to leave everything alone. the workarounds are known, and
not overly onerous to get around.


--
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email