* Thorsten Glaser <[email protected]>, 2011-08-23, 16:44:
with a blog title like “Was zum ¿€&%@!#? machen die da eigentlich?”
(without the “” quotes), rss2email fails to generate something that
passes for a valid eMail header:
From: =?utf-8?b?V2FzIHp1bSDCv+KCrCYlQCEjPyBtYWNoZW4gZGllIGRhIGVpZ2VudGxpY2g/?=
<[email protected]>
So what's wrong with this header? It looks good to me.
I guess that some software might try to decode the B-encoded part first,
and then try to extract addr-spec from it. But that is broken behavior,
according to my understanding of RFC 822 and RFC 2047. Quoting §6.2 of
the latter:
| NOTE: Decoding and display of encoded-words occurs *after* a
| structured field body is parsed into tokens. It is therefore
| possible to hide 'special' characters in encoded-words which, when
| displayed, will be indistinguishable from 'special' characters in the
| surrounding text. For this and other reasons, it is NOT generally
| possible to translate a message header containing 'encoded-word's to
| an unencoded form which can be parsed by an RFC 822 mail reader.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
