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 <[email protected]>
Subject: =?utf-8?Q?Update: Twitter Apps and You=0A?=
Spaces are not allowed either:
encoded-text = 1*<Any printable ASCII character other than "?"
or SPACE>
; (but see "Use of encoded-words in message
; headers", section 5)
At least they did actually use Q-P encoding, although completely unnecessary
since the encoded character is a newline.
me
