On Thu, Sep 02, 2010 at 03:11:30PM -0700, Michael Elkins wrote:
On Thu, Sep 02, 2010 at 02:49:00PM -0700, Michael Elkins wrote:The problem is that the sender's MUA has not produced a valid RFC2047 encoding. Here is the ABNF (RFC2047, section 2, "Syntax of encoded-words"):Conincidentally, it appears that even Twitter doesn't get this right. From an email that I just received:From: Twitter <twitter-bulkr-me=sigpipe....@postmaster.twitter.com> Subject: =?utf-8?Q?Update: Twitter Apps and You=0A?= Spaces are not allowed either:
Does mutt rely on the fact that encoded-text shouldn't have "?" or SPACE because it makes the implementation easier? Or is it just following the RFC strictly? Reading the RFC, it's not clear to me *why* encoded-text can't have "?" or SPACE.
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? Ed
signature.txt
Description: Digital signature
