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

Top Page
Delete this message
Reply to this message
Author: Derrick
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




--- Comment #3 from Derrick <derrick.rice@???> 2008-10-24 00:55:45 ---
(In reply to comment #2)
> To Derrick: what is BR?


Sorry, replace BR with CR. I had 'break' in my head.

> I don't think the separator used in ${rfc2047: should change, since sites which
> use a ${sg of SPACE into LF SPACE (as suggested above) will see their
> configuration break (you get to LF in a row, ending the headers).


This is true, but this occurs because rfc2047 had this deficit to begin with,
and users started using this workaround (as suggested above). The correct 2047
behavior would insert these LF's, rather than expect them to be inserted with a
conditional ${sg.

But yes, not breaking existing configurations seems the appropriate course,
here. Documentation ought to be updated to indicate that rfc2047 doesn't
actually follow rfc2047 to the letter.
http://exim.org/exim-html-current/doc/html/spec_html/ch11.html#SECTexpop

I don't have a good understanding of $h_ right now, so I'll look into that
further before commenting on your suggestion there.


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