What is address internationalization (EAI)?
Still have a question, spotted an error, or have a better explanation or a source we should cite?
Email Address Internationalization (EAI) means email addresses can contain characters from any language. Not just English letters and numbers. Real Greek, Cyrillic, Japanese, Arabic. In both the username part (before the @) and the domain part (after it).
So instead of being stuck with captain@ship.com, you could send from капитан@корабль.рф (Russian) or 船長@船.jp (Japanese). Your address matches your actual name and language.
Technically, EAI works through an SMTP extension called SMTPUTF8 (from RFC 6531). When a mail server supports it, it can handle Unicode characters in addresses. Domains use something called IDNA and punycode behind the scenes. The human-readable domain (like 船.jp) gets converted into ASCII that DNS can process, then converted back for display.
The practical problem: support is patchy. Older systems, web forms, and even some modern ESPs still assume addresses are plain ASCII. If you set your reply-to as привет@example.ru, some subscribers won't be able to respond. Their mail client might reject it as invalid. Same goes for signup forms that validate email addresses with outdated regex patterns.
That's why most senders keep a traditional ASCII address as their primary contact, even if they experiment with EAI addresses. You can use an internationalized address in the visible "From" name, but the actual email address behind it stays ASCII. Safer that way.
Where EAI matters most: companies operating in non-Latin markets (Russia, China, Japan, Middle East) where customers expect to interact in their native script. For English-language senders, this isn't urgent. For everyone else, it's a growing expectation that email infrastructure is slowly catching up to.
Contributors
Who worked on this answer
Every name links to their profile. Every company links to their site. Real people, real accountability.
