Internet-Draft SMTPUTF8 Email Addresses November 2026
Gulbrandsen & Yao Expires 20 May 2027 [Page]
Workgroup:
mailmaint
Internet-Draft:
draft-ietf-mailmaint-smtputf8-syntax-07
Updates:
6532 (if approved)
Published:
Intended Status:
Standards Track
Expires:
Authors:
A. Gulbrandsen
ICANN
J. Yao
CNNIC

SMTPUTF8 Email Addresses

Abstract

This document updates the email address syntax to include the addresses in active use, include the addresses likely to be used based on what writing systems are used together, and exclude addresses that pose risks when recipient software renders or processes them.

Discussion Venues

This note is to be removed before publishing as an RFC.

Discussion of this document takes place on the Mail Maintenance Working Group mailing list (mailmaint@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/mailmaint/.

Source for this draft and an issue tracker can be found at https://github.com/arnt/mailmaint-smtputf8.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 20 May 2027.

▲

Table of Contents

1. Introduction

[RFC6531] extends SMTP and [RFC6532] extends message syntax to support non-ASCII both in localparts and domain parts. In addition, some email software supports Unicode in domain parts by using encoded domain parts in the SMTP transaction ("RCPT TO:info@xn--dmi-0na.fo") and presenting the Unicode version (dømi.fo in this case) in the user interface.

The email address syntax extension in [RFC6532] allows almost all UTF-8 strings as localparts. While this certainly allows everything users want to use, it is also flexible enough to allow many things that users and implementers find surprising and sometimes worrying. For example, the domain extracted by code may not match that shown to users on-screen.

This document defines rules that allow the addresses currently used and the addresses that users and implementers have asked for. It disallows addresses that cause confusing rendering, including many instances of homographic rendering. It does not try to disallow anything that is already disallowed by IDNA (see [RFC5891]) or by common registry policies (see [IDN-TABLES]).

2. Requirements Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

3. Terminology

Script, in this document, refers to the Unicode script property (see [UAX24]). Each code point is assigned to one script ("a" is Latin), except that some are assigned to "Common" or a few other special values. "Latin" and "Cyrillic" are examples of scripts.

Latin refers to those code points that have the script property "Latin" in Unicode. Orléans in France and Münster in Germany both have Latin names in this document. It also refers to combinations of those code points and combining characters, and to strings that contain no code points from other scripts.

Han, Cyrillic etc. refer to those code points that have the respective script property in Unicode, as well as to strings that contain no code points from other scripts.

ASCII refers to the first 128 code points within Unicode, which includes the letters A-Z but not É or Ü. It also refers to strings that contain only ASCII code points.

Non-ASCII refers to Unicode code points except the first 128, and also to strings that contain at least one such code point.

By way of example, the address info@dømi.fo is Latin and non-ASCII, its localpart is Latin and ASCII, and its domain part is Latin and non-ASCII. 中国 is a Han string in this document, but 阿Q正传 is neither a Latin string nor a Han string, because it contains a Latin Q and three Han code points.

The term A-label is defined in [RFC5890] section 2.3.2.1.

PRECIS is described in [RFC8264], and the IdentifierClass in section 4.2 of that document.

4. Rules

The following four rules apply to the [I-D.ietf-emailcore-rfc5322bis] mailbox production, as indirectly extended by [RFC6532].

  1. An atom in an address MUST NOT be an A-label (e.g. xn--dmi-0na).

  2. An address MUST contain only code points that the PRECIS IdentifierClass treats as valid, and the U+0020 space. Where the IdentifierClass requires a contextual rule, the address MUST satisfy that rule (defined in [RFC8264] and described in depth in [RFC5892] Appendix A).

  3. An address MUST NOT contain more than one script, when ASCII is disregarded. Three groups of scripts are permitted: Han, Hiragana and Katakana, Han and Hangul, and finally Han and Bopomofo. (For example: In the word Orléans, Orl and ans are ASCII and é is non-ASCII. Disregarding ASCII leaves a single é, necessarily a single script, so the word contains only one script. Another example: まり子 is Hiragana and Han, which count as one.)

  4. An address MUST be in the Unicode NFC form (see [UAX15]).

These rules do not affect rules in other documents. Most notably, the domain-name production in an in email addresses is almost always also a domain names on the public internet, which implies that the rules specified by [RFC952], [RFC5891] and others affect email addresses. Domain registries often have policies regarding which names may be registered.

These rules constrain how to generate email addresses in email messages. This document does not require receivers to reject, alter or normalize non-conforming addresses.

5. Examples

example@example.com is permitted, because 1) it does not contain any A-label, 2) it consists entirely of permissible code points, 3) it contains no non-ASCII code points at all and 4) it is in NFC form.

The address dømi@dømi.fo is permitted, because 1) it does not contain any A-label, 2) the IdentifierClass permits every code point in it, 3) it consists entirely of 'Latin' and 'Common' code points and 4) it is in NFC form.

The address U+200E '@' U+200F '.' U+200E is not permitted, because 2) the IdentifierClass disallows U+200E and U+200F as ignorable code points.

The address 'admin' U+3164 '@example.com' is not permitted for the same reason. U+3164 HANGUL FILLER renders as nothing at all, so the address looks exactly like admin@example.com.

The address まり子@まり子.日本 is permitted, because 1) it contains no A-label, 2) the IdentifierClass permits every code point in it, 3) Hiragana and Han count as one script and 4) it is in NFC form.

阿Q正传@阿Q正传.example is permitted because it contains ASCII and Han, dømi@dømi.fo is permitted because it contains ASCII and Latin, but 阿Q正传@dømi.fo is not, because it contains both Han (阿) and Latin non-ASCII (ø), and 지훈@まり子.日本 is not because contains both Hangul and Hiragana.

example@-example-.example.com is permitted by the rules above. However, since [RFC952] and its successors prohibit both of the hyphens, that email address is effectively not permitted on the internet.

6. Old stored messages

This section is informative.

A mailstore may contain old messages that do not conform to the rules of this document, or indeed any RFC. Two typical examples may be To: info@xn--dmi-0na.fo and To: =?ISO-8859-1?Q?info@d=F8mi.fo?=. A more confusing example is "ali" U+202E "moc.elpmaxe@kravdraa.ec", which could be rendered as alice.aardvark@example.com (U+202E changes display direction). It is advisable to be careful about how to display an address to users if that address does not conform to the rules in this document.

7. Relationships to other RFCs

This section is informative.

This document does not update [RFC6531]. This is because the ABNF in [RFC6531] permits everything this document needs, and the restrictions in this document are not needed within SMTP. (For example, while a human recipient might be confused by a homograph attack or a hard-to-read A-label, a receiving SMTP server can hardly be.)

However, a program that acts as an SMTP client is almost inevitably affected. This document requires such program to ensure that the addresses used in the message (To, Cc etc) are normalised. In a large majority of cases, the addresses in To/Cc are also used in RCPT TO. Whether this document updates [RFC6531] formally or merely affects all implementations is a good question.

If it updatesthe document, then this document should perhaps say something like "the SMTP server MAY normalize addresses when looking up a destination to perform delivery, but is not required to".

8. IANA Considerations

This document does not require any actions from the IANA.

9. Security Considerations

When a program renders a non-ASCII email address string on-screen or stores it as a string (e.g. as part of a line of text in a system log file), the address eventually shown to a human may not be as desired. One possible way to diminish the risk is to replace impermissible code points with U+FFFD, REPLACEMENT CHARACTER. There are also other options. Note that changing an entire email message in this way risks invalidating signatures such as DKIM.

The rules in this document permit a number of code points that can make an address difficult to cut and paste.

[RFC5321] section 4.1.2 advises those who define mailboxes to avoid case-sensitive localparts, and [RFC6530] section 10.1 advises them to support other normalization forms of the same localpart. [RFC8264] section 5.2.3 discusses some options for case mapping. When processing addresses in remote domains, one cannot be sure which conversion rules apply. Implementers may want to consider unusual cases such as the Turkish dotless ı.

10. References

10.1. Normative References

[I-D.ietf-emailcore-rfc5322bis]
Resnick, P., "Internet Message Format", Work in Progress, Internet-Draft, draft-ietf-emailcore-rfc5322bis-12, , <https://datatracker.ietf.org/doc/html/draft-ietf-emailcore-rfc5322bis-12>.
[RFC5890]
Klensin, J., "Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework", RFC 5890, DOI 10.17487/RFC5890, , <https://www.rfc-editor.org/rfc/rfc5890>.
[RFC5892]
Faltstrom, P., Ed., "The Unicode Code Points and Internationalized Domain Names for Applications (IDNA)", RFC 5892, DOI 10.17487/RFC5892, , <https://www.rfc-editor.org/rfc/rfc5892>.
[RFC6531]
Yao, J. and W. Mao, "SMTP Extension for Internationalized Email", RFC 6531, DOI 10.17487/RFC6531, , <https://www.rfc-editor.org/rfc/rfc6531>.
[RFC6532]
Yang, A., Steele, S., and N. Freed, "Internationalized Email Headers", RFC 6532, DOI 10.17487/RFC6532, , <https://www.rfc-editor.org/rfc/rfc6532>.
[RFC8264]
Saint-Andre, P. and M. Blanchet, "PRECIS Framework: Preparation, Enforcement, and Comparison of Internationalized Strings in Application Protocols", RFC 8264, DOI 10.17487/RFC8264, , <https://www.rfc-editor.org/rfc/rfc8264>.
[UAX15]
Whistler, K., "Unicode Normalization Forms", , <https://www.unicode.org/reports/tr15>.
[UAX24]
Whistler, K., "Unicode Script Property", , <https://unicode.org/reports/tr24>.
[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/rfc/rfc2119>.
[RFC8174]
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/rfc/rfc8174>.

10.2. Informative References

[RFC952]
Harrenstien, K., Stahl, M., and E. Feinler, "DoD Internet host table specification", RFC 952, DOI 10.17487/RFC952, , <https://www.rfc-editor.org/rfc/rfc952>.
[RFC5321]
Klensin, J., "Simple Mail Transfer Protocol", RFC 5321, DOI 10.17487/RFC5321, , <https://www.rfc-editor.org/rfc/rfc5321>.
[RFC5891]
Klensin, J., "Internationalized Domain Names in Applications (IDNA): Protocol", RFC 5891, DOI 10.17487/RFC5891, , <https://www.rfc-editor.org/rfc/rfc5891>.
[RFC6530]
Klensin, J. and Y. Ko, "Overview and Framework for Internationalized Email", RFC 6530, DOI 10.17487/RFC6530, , <https://www.rfc-editor.org/rfc/rfc6530>.
[IDN-TABLES]
IANA, "Repository of IDN Practices", n.d., <https://www.iana.org/domains/idn-tables>.

Appendix A. Acknowledgments

The authors wish to thank John C. Klensin, Daniel Eggert, Andrew Gallagher, Jeffrey Stedfast, Pete Resnick, Narendra Singh Bisht, Collin Anderson (your name here, please)

(Wow, the ack section is already outdated)

Dømi.fo and 例子.中国 are reserved by nic.fo and CNNIC for use in examples and documentation.

阿Q正传 is a famous Chinese novella, 阿Q is the main character.

Appendix B. Instructions to the RFC editor

Please remove the Open Issues section.

This document uses the form U+0020 to refer to Unicode code points. Please change that to the form most commonly used in newish RFCs — or leave it if there is no dominant form. I'm too lazy to count today.

Appendix C. Testing

This is a set of test addresses in JSON format.

Below is a verbatim copy of https://github.com/arnt/mailmaint-smtputf8/blob/main/tests.json as it was on (date here). It contains a number of strange and unusual code points, so cutting and pasting this may not work. Rather, it is recommended to either use the rfcstrip tool or download the tests using a command such as curl https://raw.githubusercontent.com/arnt/mailmaint-smtputf8/main/tests.json > tests.json.

Note to IETF reviewers: The tests will be included here shortly before publication (and after IETF Last Call).

Appendix D. Open issues

  1. Update 6531?

Authors' Addresses

Arnt Gulbrandsen
ICANN
6 Rond Point Schumann, Bd. 1
1040 Brussels
Belgium
Jiankang Yao
CNNIC
No.4 South 4th Zhongguancun Street
Beijing
100190
China