RFC 5336: SMTP Extension for Internationalized Email Addresses
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6531.
Current version: RFC 6531 — SMTP Extension for Internationalized Email
In plain English — editorial summary, not part of the RFC
This document specifies an SMTP extension for transport and delivery of email messages with internationalized email addresses or header information. Communication with systems that do not implement this specification is specified in another document. This document updates some syntaxes and rules defined in RFC 2821 and RFC 2822, and has some material updating RFC 4952This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC5336
- Published
- September 2008
- Authors
- J. Yao; W. Mao
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- app
- Pages
- 22
- Also known as
- —
- Obsoleted by:
- RFC 6531
Topics
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 5504Downgrading Mechanism for Email Address InternationalizationObsoleted
March 2009
- RFC 5825Displaying Downgraded Messages for Email Address InternationalizationObsoleted
April 2010
- RFC 6857Post-Delivery Message Downgrading for Internationalized Email MessagesCurrent
March 2013
- RFC 2936HTTP MIME Type Handler DetectionCurrent
September 2000
- RFC 2156MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIMECurrent
January 1998
- RFC 1893Enhanced Mail System Status CodesObsoleted
January 1996
- RFC 1891SMTP Service Extension for Delivery Status NotificationsObsoleted
January 1996
- RFC 1869SMTP Service ExtensionsObsoleted
November 1995
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?