RFC 6855: IMAP Support for UTF-8
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9755.
Current document in this lineage: RFC 9755 — IMAP Support for UTF-8
In plain English — editorial summary, not part of the RFC
This specification extends the Internet Message Access Protocol (IMAP) to support UTF-8 encoded international characters in user names, mail addresses, and message headers. This specification replaces RFC 5738.
Document record
- Document ID
- RFC6855
- Published
- March 2013
- Authors
- P. Resnick; C. Newman; S. Shen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 12
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 5738 (2010)
- RFC 6855 (2013)
- RFC 9755 (2025) ✓
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6851Internet Message Access Protocol (IMAP) - MOVE ExtensionCurrent
January 2013
- RFC 7162IMAP Extensions: Quick Flag Changes Resynchronization (CONDSTORE) and Quick Mailbox Resynchronization (QRESYNC)Current
May 2014
- RFC 6154IMAP LIST Extension for Special-Use MailboxesCurrent
March 2011
- RFC 5892The Unicode Code Points and Internationalized Domain Names for Applications (IDNA)Updated
August 2010
- RFC 5616Streaming Internet Messaging AttachmentsCurrent
August 2009
- RFC 5550The Internet Email to Support Diverse Service Environments (Lemonade) ProfileCurrent
August 2009
- RFC 5524Extended URLFETCH for Binary and Converted PartsCurrent
May 2009
- RFC 5423Internet Message Store EventsCurrent
March 2009
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?