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

Top Page
Delete this message
Reply to this message
Author: Brad "anomie" Jorsch
Date:  
To: exim-dev
Old-Topics: [exim-dev] [Bug 638] New: rfc2047 encoding doesn't work correctly
Subject: [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

Brad "anomie" Jorsch <anomie@???> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |anomie@???





--- Comment #5 from Brad "anomie" Jorsch <anomie@???> 2008-10-24 14:31:57 ---
(In reply to comment #4)

Actually, RFC 2047 does specify the length of lines:

> An 'encoded-word' may not be more than 75 characters long, including
> 'charset', 'encoding', 'encoded-text', and delimiters. If it is
> desirable to encode more text than will fit in an 'encoded-word' of
> 75 characters, multiple 'encoded-word's (separated by CRLF SPACE) may
> be used.
>
> While there is no limit to the length of a multiple-line header
> field, each line of a header field that contains one or more
> 'encoded-word's is limited to 76 characters.



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