Support for third-party internationalized email addresses in Gmail

["Kevin A. McGrail" <KM...@PCCC.com>]

I wanted to bring this up because Google is moving forward with 
https://tools.ietf.org/html/rfc6530 and as they write at 
http://googleenterprise.blogspot.com/2014/08/a-first-step-toward-more-global-email.html, 
they are taking the first steps on this issue.

I expect this will break many websites and a lot of underlying 
technology will need to be upgraded to handle this.  But the writing is 
on the wall with Google as the 1000lb gorilla pushing this forward.

regards,
KAM

Support for third-party internationalized email addresses in Gmail 
<http://googleappsupdates.blogspot.com/2014/08/support-for-third-party.html> 


Posted: 06 Aug 2014 01:18 PM PDT

With this launch, Gmail users will be able to send to, and receive from, 
email addresses that contain accented or non-Latin characters. This 
includes both the domain name (to the right of the @ symbol) and/or the 
local-part (to the left of the @ symbol), as in 武＠メール.グーグル.
*
*
Google Accounts will continue to contain only non-accented Latin 
characters (ASCII <http://en.wikipedia.org/wiki/ASCII>), so users will 
not be able to create an account such as Борис@gmail.com.
*
*
Release track:
Rapid release and Scheduled release
*
*
For more information:
Enterprise Blog Post 
<http://googleenterprise.blogspot.com/2014/08/a-first-step-toward-more-global-email.html>
/
Note: all launches are applicable to all Google Apps editions unless 
otherwise noted/

*whatsnew.googleapps.com* <http://whatsnew.googleapps.com/>

** 
<http://fusion.google.com/add?source=atgs&feedurl=http%3A//feeds.feedburner.com/GoogleAppsUpdates>

Re: Support for third-party internationalized email addresses in Gmail

[Mark Martinec <Ma...@ijs.si>]

Kevin A. McGrail wrote:
> I wanted to bring this up because Google is moving forward with
> https://tools.ietf.org/html/rfc6530 and as they write at
> http://googleenterprise.blogspot.com/2014/08/a-first-step-toward-more-global-email.html,
> they are taking the first steps on this issue.
> 
> I expect this will break many websites and a lot of underlying
> technology will need to be upgraded to handle this.  But the writing
> is on the wall with Google as the 1000lb gorilla pushing this forward.

Postfix 2.12 brought support for "Internationalized Email"
SMTP service extension (SMTPUTF8) - I have it running here.

In amavisd-new I have support for RFC 6531..6533 now mostly done,
still lacking some details before a release (like ORCPT encoding).

I expect to be tracking some of the overly strict regexps and
parsing in SpamAssassin once I get amavis with EAI out of the door,
although much work will still remain to be done regarding IDN
and UTF-8 encodings of domains and localpart. Time to open
a ticket in bugzilla guess...

   Mark