Quick reference to Internet message headers

The following table lists Internet message header fields which have been defined in RFCs or actually used or both, in E-mail messages, Usenet messages, or other contexts. For each header, its name, a short description, and some reference is given; the reference tries to point to a document where the meaning of the header is specified or described. In several cases, the description is just an educated (?) guess. The use of the word nonstandard here typically means just lack of more specific information; it does not imply that other headers would necessarily be standard. This is a descriptive document, aimed at helping to find information in official and unofficial sources. This document does not cover HTTP headers; see a separate Quick reference to HTTP headers.

The alphabetic order is by words, counting a hyphen as word separator, so e.g. Mail-System-Version appears before Mailer.

Header field nameDescription References or comments
Abuse-Reports-To E-mail address for reporting abuse Inserted by some news servers
Also-ControlUsenet control message and a normal article at the same time "son-of-RFC1036": 6.15
Alternate-Recipient Controls whether the message may be forwarded to alternate recipients RFC 2156
Apparently-ToRecipients derived (by Sendmail) from message envelope when there is no To header nonstandard, discouraged, mentioned in RFC 1211
ApprovedModerator of the Usenet newsgroup, or marks certain control messages RFC 1036: 2.2.11
Approved-ByModerator of a mailing list, who approved the message Used by some mailing list expansion systems
Article-NamesReference to specially important articles for a particular Usenet newsgroup "son-of-RFC1036": 6.17
Article-Updates Similar to Supersedes but does not cause the referenced article to be physically deleted "son-of-RFC1036": 6.18
AutoforwardedHas been automatically forwarded RFC 2156
Auto-ForwardedMisspelling of Autoforwarded Appears in some documents; perhaps not actually used
bccRecipient(s) not to be disclosed to other recipients ("blind carbon copy") RFC 822: 4.5.3; RFC 1123: 5.2.15-16, 5.3.7;
Cache-Post-Path ?? Seems to appear in conjunction with X-Cache
ccSecondary, informational recipient(s) RFC 822: 4.5.2; RFC 1123: 5.2.15-16, 5.3.7;
CommentsText comments added to the message RFC 822: 4.7.2
Content-AliasUsed in addition to Content-Location if this content part can be retrieved through more than one URIWork in progress
Content-Alternative Information on where an alternative variant of this document might be found draft-ietf-fax-content-negotiation-03.txt: 4
Content-BaseBase to be used for resolving relative URIs within this content partRFC 2110
Content-Class Type information of the content in some class hierarchy Nonstandard
Content-ConversionWhether the body may be converted from a charset to anotherNonstandard variant of Conversion
Content-Description Description of a particular body part of a message RFC 2045: 8
Content-DispositionWhether MIME body part is to be shown inline or as an attachment; may also suggest a file nameRFC 1806, RFC 2183
Content-FeaturesMore detailed information about the Content-TypeNonstandard
Content-IDUnique ID of one body part of the content of a message RFC 2045: 7
Content-IdentifierA text string which identifies the content of a message RFC 2156
Content-LanguageCode for natural language used in the message RFC 1766: 3
Content-LengthSize in bytes of the message textNonstandard, discouraged
Content-LocationURI with which the content of this content part might be retrievableRFC 2110
Content-MD5Checksum of contentRFC 1864
Content-ReturnWhether the content of a message is to be returned with non-delivery notifications RFC 2156
Content-SGML-EntityInformation about the SGML entity declaration corresponding to the bodyNonstandard
Content-Transfer-EncodingCoding method used in a MIME message body RFC 2045: 6;
Content-TypeData type and format of content RFC 1049 (historic); RFC 1123: 5.2.13; RFC 2045: 5; RFC 1766: 4.1
ControlOn Usenet, indicates a control message RFC 1036: 2.1.6
ConversionWhether the body may be converted from a charset to another RFC 2156
Conversion-With-LossWhether the body may be converted from a charset to another if information will be lost RFC 2156
DateThe time when the message was written (or submitted) RFC 822: 5.1; RFC 1123: 5.2.14; RFC 1036: 2.1.2
Delivered-ToUsed for loop detection Nonstandard
Delivery-DateThe time when a message was delivered to its recipient RFC 2156
Discarded-X400-IPMS-ExtensionsX.400 IPM extensions which could not be mapped to Internet mail format RFC 2156
Discarded-X400-MTS-ExtensionsX.400 MTS extensions which could not be mapped to Internet mail format RFC 2156
Disclose-Recipients Controls whether recipients are to be told the names of other recipients RFC 2156
Disposition-Notification-OptionsOptions for notifications to be sent when the message is receivedRFC 2298
Disposition-Notification-ToRequests for notification when the message is received, and specifies the address for themRFC 2298
DistributionLimitation on where the Usenet article can be distributed RFC 1036: 2.2.7
DL-Expansion-History-IndicationTrace of distribution lists passed RFC 2156
EncodingMixed usage: content type encoding, length, or boundary informationRFC 1154 (obsolete), RFC 1505
Errors-ToAddress to which notifications are to be sent and a request to get delivery notificationsnonstandard, discouraged
Envelope-ID ? Appears in E-mail and Usenet messages, seems to relate to relaying
ExpiresSuggested expiration timeRFC 1036: 2.2.4
Expiry-DateTime at which a message loses its validity RFC 2156
FaxFax number of the originatornonstandard
FccName of file in which a copy of the message is storedNonstandard
Followup-ToUsenet group(s) to which followups to the article should be sent RFC 1036: 2.2.3
For-ApprovalPrimary recipients, who are requested to approve the information in this message or its attachmentsnonstandard
For-CommentPrimary recipients, who are requested to comment on the information in this message or its attachmentsnonstandard
For-HandlingPrimary recipients, who are requested to handle the information in this message or its attachmentsnonstandard
FromAuthor(s) or person(s) taking responsibility for the message 4.4.1; RFC 1123: 5.2.15-16, 5.3.7; RFC 1036: 2.1.1
Generate-Delivery-ReportWhether a delivery report is wanted at successful delivery RFC 2156
ImportanceA hint from the originator to the recipients about how important a message is RFC 2156; RFC 2421
In-Reply-ToReference to message which this message is a reply toRFC 822: 4.6.2
Incomplete-CopyBody parts are missingRFC 2156
Injector-InfoInformation about article's injection to UsenetInserted by Mailgate
Keywordskeywords to be used as an aid in determining if the message is interesting to the reader RFC 1036: 2.2.9
LanguageCode for natural language used in the message RFC 2156
LinesNumber of lines in the body of the message RFC 1036: 2.2.12
List-ArchiveURL to use to browse the archives of the mailing listRFC 2369
List-DigestURL to use to subscribe to the digest version of the mailing list Nonstandard
List-IDURN of the the mailing list expanderNonstandard, considered for inclusion in the protocol defined in RFC 2369
List-OwnerURL to use to send E-mail to the owner of the mailing listRFC 2369
List-PostURL to use to post to the mailing listRFC 2369
List-SoftwareInformation about the software uses in the mailing list expanderNonstandard, considered for inclusion in the protocol defined in RFC 2369
List-SubscribeURL to use to subscribe to the mailing listRFC 2369
List-UnsubscribeURL to use to unsubscribe the mailing listRFC 2369
List-URLURL for various information about the mailing list Nonstandard
Mail-Copies-ToSpecial address for copies of posted followups Mail-Copies-To Draft
Mail-Reply-Requested-ByAddress to which notifications are to be sent and a request to get delivery notificationsnonstandard, discouraged
Mail-System-Versionclient software used by the originator nonstandard
Mailerclient software used by the originator nonstandard
Mailing-ListInformation about mailing list Nonstandard, cf. to List-something headers
Message-IDUnique ID for the message RFC 822: 4.6.1; RFC 1036: 2.1.5
Message-TypeIndicates that this is a delivery report gatewayed from X.400 RFC 2156
MIME-Versionspecifies the version of MIME that the message format complies with RFC 2045: 4
NewsgroupsUsenet group(s) to which the article was posted nonstandard and controversial for use in E-mail
NNTP-Posting-Datetime of posting to Usenetappears in Usenet messages
NNTP-Posting-Hosthost that posted the article to Usenetappears in Usenet messages; contains name and/or IP address
NNTP-Posting-Timetime of posting to Usenetappears in Usenet messages, variant of the more common NNTP-Posting-Date
NNTP-Proxy-RelayHost that relayed the message to Usenet Seems to appear in conjunction with NNTP-Posting-Host
ObsoletesReference to previous message being corrected and replaced RFC 2156
Old-Date? Nonstandard, used by some mailing list software
Old-X-Envelope-From? Nonstandard, used by some mailing list software
Old-X-Envelope-To? Nonstandard, used by some mailing list software
Organisation(Misspelled Organization)Nonstandard
OrganizationThe organization to which the sender belongs, or to which the machine belongs RFC 1036: 2.2.8
Original-Encoded-Information-Types Which body part types occur in this message RFC 2156
Original-RecipientOriginal recipient information for inclusion in disposition notificationsRFC 2298
Originating-Clientclient software used by the originatorNonstandard
Originatorused the same way as Sender sometimes used in Usenet, nonstandard
Originator-InfoInformation about the authentication of the originatorInternet-Draft draft-newman-msgheader-originfo-05.txt
Pathlist of MTAs which the (Usenet) message has passed RFC 1036: 2.1.6
PhonePhone number of originatorNonstandard
PICS-LabelRatings label to control selection (filtering) of messages according to the PICS protocolPICS 1.1
Posted-ToNewsgroup to which the message has been posted Appears in E-mail messages
PrecedenceMixed usage: priority value, control of automatic replies or return-of-content faciliries, prevention of mailing list loops Nonstandard, controversial
Prevent-NonDelivery-Report Whether non-delivery report is wanted at delivery error RFC 2156
PriorityPriority for message delivery RFC 2156
Read-Receipt-ToAddress to which notifications are to be sent and a request to get delivery notificationsnonstandard, discouraged
Receivedtrace of MTAs which the message has passed RFC 822: 4.3.2; RFC 1123: 5.2.8
ReferencesIn E-mail: reference to other related messages; in Usenet: reference to replied-to-articlesRFC 822: 4.6.3; RFC 1036: 2.2.5
ReplacesSpecifies previous message being corrected and replaced Proposed in UseFor: draft-ietf-usefor-article-03.txt: 6.13 >
Reply-ByLatest time at which a reply is requested RFC 2156
Reply-ToSuggested E-mail address for replies RFC 822: 4.4.3; RFC 1036: 2.2.1
Resent-bcc The bcc of a forwarded message RFC 822: 4.5.3
Resent-cc The cc of a forwarded message RFC 822: 4.5.2
Resent-Date The Date of a forwarded message RFC 822
Resent-From The From of a forwarded message RFC 822: 4.4.1
Resent-Message-ID The Message-ID of a forwarded message RFC 822: 4.6.1
Resent-Reply-To The Reply-To of a forwarded message RFC 822: 4.4.3
Resent-Sender The Sender of a forwarded message RFC 822: 4.4.2
Resent-Subject The Subject of a forwarded message Nonstandard
Resent-To The To of a forwarded message RFC 822: 4.5.1
Return-Pathdata passed from MAIL FROM: envelopeRFC 821: 4.1.1; RFC 1123: 5.2.13
Return-Receipt-RequestedAddress to which notifications are to be sent and a request to get delivery notificationsnonstandard, discouraged
Return-Receipt-ToAddress to which notifications are to be sent and a request to get delivery notificationsnonstandard, discouraged
See-AlsoReferences to related articles (other than precursors) in Usenet "son-of-RFC1036": 6.16
SenderThe person or agent submitting the message to the network, if other than shown by the From header RFC 822: 4.4.2; RFC 1123: 5.2.15-16, 5.3.7; RFC 1036: 2.1.1
SensitivityHow sensitive it is to disclose this message to other people than the specified recipients RFC 2156; RFC 2421
Speech-ActSpeech act categorization of the messageNonstandard
StatusStatus of delivery for the message when stored Non-standard, should never appear in mail in transit
SubjectText that provides a summary, or indicates the nature, of the message RFC 822: 4.7.1; RFC 1036: 2.1.4
SummaryShort text describing a longer article RFC 1036: 2.2.10
SupersedesSpecifies previous message being corrected and replaced "son-of-RFC1036": 6.14
TelefaxFax number of the originatornonstandard
ToPrimary recipient(s) RFC 822: 4.5.1; RFC 1123: 5.2.15-16, 5.3.7;
Translated-ByMailbox of the person who made the translationNonstandard
Translation-OfReference to a message which the current message is a translation ofNonstandard
User-Agentclient software used by the originator nonstandard, but often used; standardization proposed in UseFor draft draft-ietf-usefor-article-03.txt: 6.16
X-Abuse-Infoinformation for reporting abusenonstandard, appears in Usenet, in conjunction with X-Complaints-To or X-Report
X-Accept-LanguageLanguage preference(s) nonstandard, appears in Usenet and E-mail as inserted by Netscape; cf. to Accept-Language in HTTP headers
X-AdminE-mail address of news server administration Inserted by AOL software
X-Article-Creation-DateTime of original creation of the article Inserted by Deja when posting via My Deja
X-AttributionThe name under which the sender would like to appear in attributions when the message is quoted Typically a nickname; see e.g. Attribution Preferences in Supercite
X-Authenticated-IPApparently the IP address of the host of the sender Nonstandard
X-Authenticated-SenderApparently some identification of the sender Nonstandard
X-Authentication-Warning Some warning Inserted by Pine and MH in some situations
X-CacheInformation about caching server software Inserted by NNTPcache servers
X-CommentsComments, usually some disclaimer Inserted by Newsfeeds software, which uses X-Comments2 and X-Comments3, too, for continuation lines
X-Complaints-ToAn E-mail address for sending complaints on the adequacy of the Usenet message nonstandard; often appears in Usenet postings as automatically inserted by news servers
X-Confirm-reading-toAddress to which notifications are to be sent and a request to get delivery notificationsnonstandard, discouraged
X-Envelope-FromSender, as extracted from the envelope nonstandard; some mail servers add this field sometimes
X-Envelope-ToRecipient, as extracted from the envelope nonstandard; some mail servers add this field sometimes
X-Facepicture of sender's face (a 48×48 bitmap)an old invention; see e.g. About X-Face
X-Flags?Inserted by BugTraq
X-FolderFolder for saving the messageUsed by Forté software
X-Http-ProxyInformation about using Deja for posting, including the sender's IP address Inserted by Deja when posting via My Deja
X-Http-User-AgentWeb browser used for posting Inserted by Deja when posting via My Deja
X-IMAPUID as defined in IMAP Nonstandard; only for internal mailbox format
X-Last-Updated time of most recent update Appears in FAQ postings on Usenet
X-List-HostAs List-SoftwareNonstandard,
X-ListserverAs List-SoftwareNonstandard
X-LoopUsed for loop detection Nonstandard
X-Mailerclient software used by the originator nonstandard
X-Mailer-InfoURL for info about client software used by the originator nonstandard
X-Mailing-ListInformation about mailing list Nonstandard, cf. to List-something headers
X-MIME-AutoconvertedInformation about conversion of this message on the path from sender to recipient Nonstandard
X-MimeOLEinformation about client software used by the originator nonstandard, appears in Usenet articles sent by Outlook Express
X-MIMETrackInfo about the message passing through a router Nonstandard
X-MSMail-PriorityYet another priority indication nonstandard, appears in Usenet articles sent by Outlook Express
X-MyDeja-InfoInternal user id Inserted by Deja when posting via My Deja
X-Newsreaderclient software used by the originator nonstandard; often appears in Usenet messages
X-NNTP-Posting-Host Posting host Variant of NNTP-Posting-Host
X-No-ArchiveDo not archive the message in publicly available archivesNonstandard; seems to be honored e.g. by Deja
X-NoticeA comment on reporting abuse Inserted by some news servers
X-Orig-Message-IDOriginal Message-ID Appears in relayed messages
X-Original-Envelope-From E-mail address of original sender Nonstandard
X-Original-NNTP-Posting-Host Name or IP address of the original posting host Appears in Usenet postings, assumably inserted by an ISP's news server, for tracing back the computer that the customer used for posting
X-Original-Trace Information (host, time, etc.) about the original posting Appears in Usenet postings, assumably inserted by an ISP's news server, for tracing back the event of the customer's original posting; cf. to X-Trace
X-OriginalArrivalTime Time when the message was delivered into the message transport system Nonstandard
X-Originating-IPApparently the IP address of the host of the sender Nonstandard
X-PMFLAGSInternal flags indicating message status Used by Pegasus, assumably for its internal bookkeeping only and shouldn't appear in outgoing mail
X-Posted-ByAttempted identification of the sender Nonstandard
X-Posting-Agentclient software used by the originator nonstandard; often appears in Usenet messages
X-PriorityPriority for message delivery Eudora Pro Macintosh User Manual, Qualcomm Inc., 1988-1995
X-RCPT-TOIndication of recipient on the SMTP envelope Nonstandard
X-ReportInformation about reporting abuse Inserted by Newsfeeds software
X-Report-Abuse-ToInformation about reporting abuse Yet another variant of a theme
X-Senderused similarly to Sender but often indicating that you may not be able to send E-mail to this address practice described (as non-standard) in Common Internet Message Header Fields
X-Server-DateSome time denotation Assumably indicates when the original news server received the posting
X-TraceInformation about postingNonstandard, appears in Usenet messages; usually contains posting host name and/or IP address and posting time, perhaps other tracing information too
X-UIDLUnique ID for the message, local to a particular local mailbox storeNonstandard; the POP 3 specification defines the UIDL identifier but not the X-UIDL header
X-UML-Sequence? Inserted by some mailing list programs
X-URISometimes used with the same meaning as Content-Location, sometimes to indicate the Web home page of the sender or of his organisationNonstandard
X-URLSimilar usage as X-URINonstandard
X-X-Sendersimilar to X-Sender practice described (as non-standard) in Common Internet Message Header Fields
X400-Content-ReturnPossible future name for Content-Returnnonstandard
XPident Appears, usually with value unknown, in Usenet postings
XrefIdentification of a message within a server RFC 1036: 2.2.13; only for local use within a Usenet news server

Notes on header names in general:

There is surely a much larger set of X- headers used somewhere than the list above tells. It could be some sort of sports to add headers just for fun, on user agents that allow arbitrary headers to be inserted. Examples:
X-Anagram: look vanilla, aim elite
X-Eric-Conspiracy: there is no conspiracy

Explanations of abbreviations:

MIME
Multipurpose Internet Mail Extensions, a set of specifications for extending the format of Internet E-mail to allow non-US-ASCII textual messages, non-textual messages, multipart message bodies, and non-US-ASCII information in message headers; used outside E-mail too
MTA
Message Transfer Agent, generically a program responsible for delivering E-mail messages
PICS
Platform for Internet Content Selection, a method for associating metadata (PICS labels) to be associated with Internet content, so that users can filter content; originally designed to help parents and teachers control what children access on the Internet.

This document basically tries to combine some content from July 2000 version of the Internet-draft Common Internet Message Header Fields, (a planned revision of RFC 2076; there's now a newer version of the draft available) with observations from headers actually used in different contexts. Information about the following headers has been taken from other sources: Abuse-Reports-To, Cache-Post-Path, Envelope-ID, Injector-Info, Mail-Copies-To, NNTP-Posting-Date, NNTP-Posting-Host, NNTP-Posting-Time, NNTP-Proxy-Relay, Old-Date, Old-X-Envelope-From, Old-X-Envelope-To, Posted-To, User-Agent, X-Abuse-Info, X-Accept-Language, X-Admin, X-Article-Creation-Date, X-Attribution, X-Authenticated-ID, X-Authenticated-Sender, X-Authenticated-User, X-Authentication-Warning, X-Cache, X-Comments X-Complaints-To, X-Face, X-Flags, X-Folder, X-Http-Proxy, X-Http-User-Agent, X-Mailing-List, X-MSMail-Priority, X-MyDeja-Info, X-NNTP-Posting-Host, X-Notice, X-Orig-Message-ID, X-Original-Envelope-From, X-Original-NNTP-Posting-Host, X-Original-Trace, X-Originating-IP, X-PMFLAGS, X-Posted-By, X-Posting-Agent, X-Report, X-Report-Abuse-To, X-Server-Date, X-Trace, X-UML-Sequence, XPident.