--On Thursday, March 5, 2020 23:40 -0500 John R Levine
<johnl(_at_)taugh(_dot_)com> wrote:
On Fri, 6 Mar 2020, Mark Andrews wrote:
Conversion of all ASCII headers to utf-8 mime encoded should
be banned. Apart from testing encoding/decoding it serves no
useful purpose and if you want to perform such testing you
can always add a non ASCII character. MUA's that do this
are deliberately breaking interoperability with old MUAs.
The spec is pretty clear where you can have MIME entities and
where you can't. You can't have them in Message-ID's,
References, or the actual address in To, From, Cc, etc.
In the interest of clarity, what you are referring to as "MIME
entities" are encoded words as specified in RFC 2231. Right?
And because encoded words are not permitted in Message-IDs or
the other fields you mention, those fields must conform to the
specified syntax without decoding. If they don't, it is pretty
much up to the receiving system what to do about it. I suppose
that could including treating the strings as encoded works and
see where decoding takes one, but that would be so far beyond
the standard that questions about the decoded (UTF-8 or
otherwise) field looks like are really not relevant here: such a
string is either valid or invalid without decoding and, as far
as the standard is concerned, that is the end of it.
john
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp