Negotiate SMTPUTF8 before transporting internationalized addresses

Frame this document as a source-led configuration and assurance check: Negotiate SMTPUTF8 before transporting internationalized addresses. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official RFC 6531 — SMTP Extension for Internationalized Email from RFC Editor / Internet Engineering Task Force supports the following bounded statements:

• An SMTP server advertising SMTPUTF8 accepts UTF-8 wherever the SMTP mailbox grammar permits a mailbox value. The research record locates this support at Section 3.2 (The SMTPUTF8 Extension).
• A client may send internationalized mailbox names and UTF-8 headers only after the server advertises SMTPUTF8 in its EHLO response. The research record locates this support at Section 3.2 (The SMTPUTF8 Extension), negotiation rule.
• If the next SMTP server lacks SMTPUTF8, the client must not transmit the internationalized message and instead transforms, rejects, requeues, or tries another MX as permitted. The research record locates this support at Sections 3.2 (The SMTPUTF8 Extension) and 3.5 (Non-ASCII Addresses and Reply-Codes).

The source support ends with the statements listed above. Use them to examine sending domains, receiving domains, message agents, headers, authentication results, policy records, and failure handling in the applicable environment, not to imply a wider guarantee.

What the source does not establish

This RFC evidence supports only the named mail-protocol decision; it does not prove provider support, deliverability, or compliance for a particular flow. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine authoritative DNS, certificates, time, gateways, identity stores, reputation services, and third-party mail providers before translating the source into an operational decision.

Applicability questions

• For source statement 1 at Section 3.2 (The SMTPUTF8 Extension), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Section 3.2 (The SMTPUTF8 Extension), negotiation rule, which observable configuration, record, or test can confirm applicability here?
• For source statement 3 at Sections 3.2 (The SMTPUTF8 Extension) and 3.5 (Non-ASCII Addresses and Reply-Codes), which observable configuration, record, or test can confirm applicability here?
• Within sending domains, receiving domains, message agents, headers, authentication results, policy records, and failure handling, which versions, roles, and configuration states define the review population?
• Could authoritative DNS, certificates, time, gateways, identity stores, reputation services, and third-party mail providers invalidate the test, hide a failure, or change applicability?
• Who owns the decision, and which observation requires stopping, escalation, or rollback?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of sending domains, receiving domains, message agents, headers, authentication results, policy records, and failure handling, observed and expected states, owner, and reason for deviation.

Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify authoritative DNS, certificates, time, gateways, identity stores, reputation services, and third-party mail providers. Handle credentials, keys, recovery data, and personal information through approved secure channels.

Verification and evidence

A reviewer should be able to retrace the decision from Section 3.2 (The SMTPUTF8 Extension); Section 3.2 (The SMTPUTF8 Extension), negotiation rule; Sections 3.2 (The SMTPUTF8 Extension) and 3.5 (Non-ASCII Addresses and Reply-Codes) through sanitized messages, DNS records, SMTP transcripts, authentication results, policy evaluation, and delivery or rejection logs. Record what was collected, where, when, by whom, and which system or role it represents.

Preserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.

Official references

• RFC 6531 — SMTP Extension for Internationalized Email — RFC Editor / Internet Engineering Task Force