RFC 5983: Mailing Lists and Internationalized Email Addresses
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6783.
Current version: RFC 6783 — Mailing Lists and Non-ASCII Addresses
In plain English — editorial summary, not part of the RFC
This document describes considerations for mailing lists with the introduction of internationalized email addresses. This document makes some specific recommendations on how mailing lists should act in various situations. This document defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC5983
- Published
- October 2010
- Authors
- R. Gellens
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- app
- Pages
- 10
- Also known as
- —
- Obsoleted by:
- RFC 6783
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 5965An Extensible Format for Email Feedback ReportsUpdated
August 2010
- RFC 6009Sieve Email Filtering: Delivery Status Notifications and Deliver-By ExtensionsCurrent
October 2010
- RFC 5957Display-Based Address Sorting for the IMAP4 SORT ExtensionCurrent
July 2010
- RFC 5953Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)Obsoleted
August 2010
- RFC 6047iCalendar Message-Based Interoperability Protocol (iMIP)Current
December 2010
- RFC 6065Using Authentication, Authorization, and Accounting Services to Dynamically Provision View-Based Access Control Model User-to-Group MappingsCurrent
December 2010
- RFC 5894Internationalized Domain Names for Applications (IDNA): Background, Explanation, and RationaleCurrent
August 2010
- RFC 5893Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA)Current
August 2010
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?