On Mon, Apr 9, 2018 at 7:57 AM John Levine <jo...@taugh.com> wrote:

> In article <
> ofc0fea11b.05dda05c-onc125826a.0038eb98-c125826a.0038f...@notes.na.collabserv.com>
> you write:
> >-=-=-=-=-=-
> >-=-=-=-=-=-
> >-=-=-=-=-=-
> >
> >Hello folks
> >
> >I've been tasked with finding out what the general consensus is on the
> >support in email headers for International characters such as  UTF-8
> >Charcacters and including things like accented characters like é and å
> and
> >can also include Asian and Cyrillic characters.
> >
> >I know there's an RFC from 2012, but my Product Dev people are interested
> >in knowing how wide-spread the actual adoption is.
> Funny you should ask.  I'm doing some work for the UASG group to document
> how
> internationalized email (known as EAI) works.
> UTF-8 in everything except the actual addresses can be in MIME body
> parts and encoded-words in mail headers.  Those have been around for
> at least a decade and should work everywhere.
> RFCs 6530-6533 defined an SMTP extension called SMTPUTF8 which, to
> oversimplify a little, allows UTF-8 anywhere you can have ASCII,
> including in both the local part and the domain part of the addresses.
> This modifies both the messages themselves and the address in the
> SMTP dialog MAIL FROM and RCPT TO.
> Uptake has been slow, but Gmail quietly added support last year, and
> Hotmail/Outlook/Live added support about a month ago.  Some of the
> large Chinese services like Coremail support it as do some Indian
> services like Xgenplus.  Yahoo/AOL/Oath have as far as I can tell no
> plans to support it.

We announced that it was supported back in 2014:

Were you referring to something else?

mailop mailing list

Reply via email to