Good news Office 365 and Exchange 2019 will support EAI addresses
Microsoft has announced that Office 365 now supports the EAI (email address internationalization) feature. And it is clear that EAI addresses will be supported in Exchange server 2019. (for more information, please refer to https://blogs.technet.microsoft.com/exchange/2018/02/26/eai-support-announcement-update/)
So what is the EAI address? (for more information, please refer to https://blogs.technet.microsoft.com/exchange/2017/12/27/eai-support-announcement/)
To put it simply, use unexpected characters from the Latin character set as part of the email address in the Email address.
Although email has become the earliest and most widely used platform for modern electronic communications, email addresses support only a limited subset of Latin characters (mainly for historical reasons). People who do not read or speak English are forced to use e-mail addresses that contain characters not used in their own language.
Many people have been working together to solve the situation. In fact, the new email standard supporting the internationalization of email addresses (rfc: 6530, 65316532, 6533) was published in 2012. However, because millions of legacy systems still exist, changes in standards are difficult to implement in the technological world.
Microsoft is pleased to announce that we are working to join the new standard. Office 365 will enable e-mail address internationalization (EAI) support in Q1 2018. As a first step, Office 365 users will be able to send and receive emails to international email addresses. Administrators can also use internationalized e-mail addresses in other Office 365 features (for example, mail flow rules for finding EAI addresses, or outbound connectors for internationalized domain name (IDN) domains). Note, however, that this new release will not support the addition of EAI addresses for office 365 users or IDN domains of office 365 organizations. We will continue to evaluate these characteristics because the standards are widely adopted. We will also keep your release plan and release it to Exchange Enterprise Edition.
