RFC 6857: Post-Delivery Message Downgrading for Internationalized Email Messages
In plain English — editorial summary, not part of the RFC
The Email Address Internationalization (SMTPUTF8) extension to SMTP allows Unicode characters encoded in UTF-8 and outside the ASCII repertoire in mail header fields. Upgraded POP and IMAP servers support internationalized messages. If a POP or IMAP client does not support Email Address Internationalization, a POP or IMAP server cannot deliver internationalized messages to the client and cannot remove the message. To avoid that situation, this document describes a mechanism for converting internationalized messages into the traditional message format. As part of the conversion process, message elements that require internationalized treatment are recoded or removed, and receivers are able to recognize that they received messages containing such elements, even if they cannot process the internationalized elements.
Document record
- Document ID
- RFC6857
- Published
- March 2013
- Authors
- K. Fujiwara
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5825Displaying Downgraded Messages for Email Address InternationalizationObsoleted
April 2010
- RFC 5504Downgrading Mechanism for Email Address InternationalizationObsoleted
March 2009
- RFC 5336SMTP Extension for Internationalized Email AddressesObsoleted
September 2008
- RFC 6783Mailing Lists and Non-ASCII AddressesCurrent
November 2012
- RFC 5721POP3 Support for UTF-8Obsoleted
February 2010
- RFC 5337Internationalized Delivery Status and Disposition NotificationsObsoleted
September 2008
- RFC 3950Tag Image File Format Fax eXtended (TIFF-FX) - image/tiff-fx MIME Sub-type RegistrationCurrent
February 2005
- RFC 3949File Format for Internet FaxCurrent
February 2005
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?