{"id":959,"date":"2018-01-10T17:20:50","date_gmt":"2018-01-10T15:20:50","guid":{"rendered":"https:\/\/msb365.abstergo.ch\/?p=959"},"modified":"2023-06-23T13:15:09","modified_gmt":"2023-06-23T11:15:09","slug":"email-address-internationalization-eai-support-office-365","status":"publish","type":"post","link":"https:\/\/www.msb365.blog\/?p=959","title":{"rendered":"Email Address Internationalization (EAI) support in Office 365"},"content":{"rendered":"<p>This Days Microsoft <a href=\"https:\/\/blogs.technet.microsoft.com\/exchange\/2017\/12\/27\/eai-support-announcement\/#comment-321205\" target=\"_blank\" rel=\"noopener\"><strong>announced<\/strong><\/a> that Office 365 will enable Email Address Internationalization (EAI) support in Q1 2018.<\/p>\n<p>This can have important implications for hybrid Exchange organisations.<br \/>\nThe announcement you can find in the Link or you simply read it here:<\/p>\n<p><span style=\"color: #0000ff;\"><em>&#8220;Out of 7.6 billion people in the world, only 360 million are native English speakers.<\/em><\/span><\/p>\n<p><span style=\"color: #0000ff;\"><em>Although email has been the earliest and most widely-adopted platform for modern electronic communication, email addresses have only supported a limited subset of Latin characters (mostly due to historical reasons). People who don&#8217;t read or speak English have been forced to use email addresses containing characters not used in their own language.<\/em><\/span><\/p>\n<p><span style=\"color: #0000ff;\"><em>Many people have been working together to try to fix this situation. In fact, new email standards to support email address internationalization (RFCs: 6530, 6531,6532, 6533) were published in 2012. However, changes in standards are difficult to implement in the world of technology due to the millions of legacy systems that are still out there.<\/em><\/span><\/p>\n<p><span style=\"color: #0000ff;\"><em>Microsoft is pleased to announce that we&#8217;re joining the effort to adopt the new standards. Office 365 will enable Email Address Internationalization (EAI) support in Q1 2018. As a first step, Office 365 users will be able to send messages to and receive messages from internationalized email addresses. Admins can also use internationalized email addresses in other Office 365 features (for example, mail flow rules that look for EAI addresses, or outbound connectors to Internationalized Domain Name (IDN) domains). But please note that this new release will not support adding EAI addresses for Office 365 users, or IDN domains for Office 365 organizations. We will continue to evaluate these features as the standards are more widely adopted. We will also keep you posted on the plan to release this to Exchange Enterprise version.&#8221;<\/em><\/span><\/p>\n<p>So what that means for us?<br \/>\nHere some examples of mail addresses which includes EAI:<br \/>\nLatin characters: petrovic@contoso.com<br \/>\nCyrillic characters: \u043f\u0435\u0442\u0440\u043e\u0432\u0438\u0446@\u0446\u043e\u043d\u0442\u043e\u0441\u043e.\u0446\u043e\u043c<br \/>\nJapanese characters: \u307at\u308d\u3094\u3043\u3063@\u304a\u3093\u3068\u305d.\u65e5\u672c<\/p>\n<p>etc.<\/p>\n<p>EAI support in Office 365 won\u2019t matter for hybrid customers if Exchange Server on-premises doesn\u2019t support it, since AD on-prem is the source of authority for email addresses. Microsoft says plans are being made to release EAI support for Exchange Server on-premises, but there are no release dates for this yet.<br \/>\nAlso important to note that the EAI RFCs also permit the use of non-ASCII characters in email headers.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>This Days Microsoft announced that Office 365 will enable Email Address Internationalization (EAI) support in Q1 2018. This can have important implications for hybrid Exchange organisations. The announcement you can find in the Link or you simply read it here: &#8220;Out of 7.6 billion people in the world, only 360 million are native English speakers. [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[1923,2],"tags":[],"class_list":["post-959","post","type-post","status-publish","format-standard","hentry","category-microsoft-365","category-exchange"],"post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/posts\/959","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=959"}],"version-history":[{"count":1,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/posts\/959\/revisions"}],"predecessor-version":[{"id":961,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/posts\/959\/revisions\/961"}],"wp:attachment":[{"href":"https:\/\/www.msb365.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=959"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=959"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=959"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}