邮件地址可以包含国际(非英语)字符吗?
更新2015年: 使用RFC 6532
实验性的5335已被6532取代,
后者被设置为“类别: 标准轨道”,
成为标准。
第3.2节(RFC 5322的语法扩展)更新了大多数文本字段以
包括(适当的)UTF-8。
The following rules extend the ABNF syntax defined in [RFC5322] and [RFC5234] in order to allow UTF-8 content. VCHAR =/ UTF8-non-ascii ctext =/ UTF8-non-ascii atext =/ UTF8-non-ascii qtext =/ UTF8-non-ascii text =/ UTF8-non-ascii ; note that this upgrades the body to UTF-8 dtext =/ UTF8-non-ascii The preceding changes mean that the following constructs now allow UTF-8: 1. Unstructured text, used in header fields like "Subject:" or "Content-description:". 2. Any construct that uses atoms, including but not limited to the local parts of addresses and Message-IDs. This includes addresses in the "for" clauses of "Received:" header fields. 3. Quoted strings. 4. Domains. Note that header field names are not on this list; these are still restricted to ASCII.
请注意明确包含的域。
和明确排除的标题名称。
关于NFKC的说明:
The UTF-8 NFKC normalization form SHOULD NOT be used because it may lose information that is needed to correctly spell some names in some unusual circumstances.
而第3节开始:
Also note that messages in this format require the use of the SMTPUTF8 extension [RFC6531] to be transferred via SMTP.