RFC 2076: Common Internet Message Headers
In plain English — editorial summary, not part of the RFC
This memo contains a table of commonly occurring headers in headings of e-mail messages. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2076
- Published
- February 1997
- Authors
- J. Palme
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 27
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1802Introducing Project Long Bud: Internet Pilot Project for the Deployment of X.500 Directory Information in Support of X.400 RoutingCurrent
June 1995
- RFC 1801MHS use of the X.500 Directory to support MHS RoutingCurrent
June 1995
- RFC 1733Distributed Electronic Mail Models in IMAP4Current
December 1994
- RFC 1732IMAP4 Compatibility with IMAP2 and IMAP2bisCurrent
December 1994
- RFC 1731IMAP4 Authentication MechanismsCurrent
December 1994
- RFC 1730Internet Message Access Protocol - Version 4Obsoleted
December 1994
- RFC 1664Using the Internet DNS to Distribute RFC1327 Mail Address Mapping TablesObsoleted
August 1994
- RFC 1544The Content-MD5 Header FieldObsoleted
November 1993
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?