On Thu, Sep 02, 2010 at 05:10:37PM -0700, Michael Elkins wrote:
On Thu, Sep 02, 2010 at 07:20:18PM -0400, Ed Blackman wrote:I forwarded the message I copied the headers from, along with a one that had spaces in the encoded-text, to my work Outlook and to my Gmail account. Both Outlook and Gmail decoded the subjects as intended, which is probably why Intrade and Twitter can get away with sending out non-conformant messages.Any chance of a rfc2047 lenient decode, perhaps as an option?Try the attached patch.
I've been running all weekend with this patch. It works for both unencoded "?" and SPACE characters in RFC2047 header lines. I searched my mail corpus for RFC2047 encoded headers (both strictly conformant and non-conformant), and couldn't find any that were incorrectly displayed, and everything else looked fine, too.
Thanks! Ed
signature.txt
Description: Digital signature
