What is SMTP UTF8 and does it affect authentication?
Still have a question, spotted an error, or have a better explanation or a source we should cite?
Most email addresses use ASCII characters: the standard Latin letters, numbers, and a few symbols. But what if your email address uses Chinese characters, Arabic script, or an accented domain like cafe@résumé.fr? That's what SMTP UTF8 is for.
SMTP UTF8 (defined in RFC 6531, also called EAI or Email Address Internationalization) extends the email infrastructure to support non-ASCII characters in both the local part and the domain of an email address. Without it, mail servers simply can't handle addresses that include characters outside the basic ASCII set.
On authentication specifically: SMTP UTF8 doesn't change how SPF, DKIM, or DMARC work conceptually. The same validation logic applies. But the implementation gets more complex. DKIM's canonicalization (the process of normalizing the message before signing) needs to handle Unicode consistently across systems. If one server normalizes differently from another, the hash won't match and DKIM fails.
In practice, most senders aren't dealing with internationalized email addresses yet. The infrastructure for SMTP UTF8 is supported by major providers but adoption among senders is limited. If you're operating in markets where non-ASCII email addresses are common (China, Japan, Arabic-speaking regions), or if you're receiving internationalized addresses on your list, it's worth knowing that authentication tooling needs to explicitly support EAI to work correctly with these addresses.
If you're validating email lists that include international addresses, our SOS hotline can help you figure out how validation tools handle EAI in your specific setup.
Contributors
Who worked on this answer
Every name links to their profile. Every company links to their site. Real people, real accountability.
