| CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 08:40:33 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=.YJL1dUmjg94dkbDRvrwCx173aTig5ARUxoZK731qGU-1760172033-1.0.1.1-0LInEJay_.Las6NcZbyKZSUcnDGD8FVWQY.jr9xaTPU4lzLNHcSgswSQ9ylu42u8u2zUeKN1J4VREu46M3jNj2LCDPRgUaF8AbOadxEvqZg; path=/; expires=Sat, 11-Oct-25 09:10:33 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98cd0d9e4e16860e-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 6855 » RFC Editor
Search RFCs
RFC 6855
IMAP Support for UTF-8, March 2013
- File formats:
- Status:
- PROPOSED STANDARD
- Obsoletes:
- RFC 5738
- Obsoleted by:
- RFC 9755
- Authors:
- P. Resnick, Ed.
C. Newman, Ed.
S. Shen, Ed. - Stream:
- IETF
- Source:
- eai (app)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC6855
Discuss this RFC: Send questions or comments to the mailing list ima@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 6855
Abstract
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us