What Is SMTPUTF8?

Internationalized addresses need transport support

SMTPUTF8 extends SMTP to support internationalized addresses and header information. The distinction is most visible when an email address contains non-ASCII characters in its local part. This is separate from writing an accented name in the body or subject, which can involve other message-format mechanisms. Seeing Unicode text in a preview does not demonstrate that an address can travel through the entire intended mail path.

An integration may accept a string while a later sending component cannot process it. A contact database, verification service, campaign uploader and mailbox provider each has its own capabilities and validation behavior. Treat those as separate boundaries. A failed upload may describe an application's limitation rather than proving that the address itself is globally invalid.

A data-handling example

A prospect supplies an internationalized business address. Preserve the original value and check whether the actual sending and receiving path supports it. Do not remove characters, replace them with guessed ASCII spellings or silently substitute a different mailbox. Such transformations can create an address that belongs to another person or does not exist, while making the source record look deceptively clean.

Verify the supported workflow

Use provider documentation and an authorized controlled test to establish which components accept and transmit the address correctly. Record the exact input, normalized representation where applicable, application response and final result. Domain-name representation and an internationalized local part are related concerns but are not interchangeable fixes; converting a domain does not automatically solve every address-handling limitation.

SMTPUTF8 support is a compatibility requirement, not a deliverability boost. It does not establish consent, business relevance or inbox placement. The operational objective is to retain the person's real address accurately and either use a supported path or explain the specific unsupported component without misclassifying the contact's identity or inventing a replacement.