| TOC |
|
This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html.
This Internet-Draft will expire on October 12, 2004.
Copyright (C) The Internet Society (2004). All Rights Reserved.
This document defines the initial IANA registration for permanent mail and MIME message header fields, per [[[RFC XXXX]]] [1].
Please send comments to <ietf-822@imc.org>. To subscribe to this list, send a message with the body 'subscribe' to <ietf-822-request@imc.org>.
| TOC |
| TOC |
This document defines IANA registration for a number of mail message and MIME header fields, per Registration procedures for message header fields[1].
[[[The main body of this document is automatically generated. Some sample HTML registry pages have been prepared from the same data, and can be found at http://www.ninebynine.org/IETF/Messaging/HdrRegistry/Intro.html.]]]
Section Registration templates contains the submission for initial registration of mail related message headers fields.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [10].
NOTE: indented comments like this provide additional nonessential information about the rationale behind this document.
[[[Editorial comments and questions about outstanding issues are provided in triple brackets like this. These working comments should be resolved and removed prior to final publication.]]]
| TOC |
Header registry entries are summarized in tabular form for convenience of reference, and presented in full in the following sections.
Header name Protocol
----------- --------
Date Mail Message date and time
From Mail Mailbox of message author
Sender Mail Mailbox of message sender
Reply-To Mail Mailbox for replies to message
To Mail Primary recipient mailbox
Cc Mail Carbon-copy recipient mailbox
Bcc Mail Blind-carbon-copy recipient
mailbox
Message-ID Mail Message identifier
In-Reply-To Mail Identify replied-to message(s)
References Mail Related message identifier(s)
Subject Mail Topic of message
Comments Mail Additional comments about the
message
Keywords Mail Message key words and/or phrases
Resent-Date Mail Date and time message is resent
Resent-From Mail Mailbox of person for whom message
is resent
Resent-Sender Mail Mailbox of person who actually
resends the message
Resent-To Mail Mailbox to which message is resent
Resent-Cc Mail Mailbox(es) to which message is
cc'ed on resend
Resent-Bcc Mail Mailbox(es) to which message is
bcc'ed on resend
Resent-Reply-To Mail Resent reply-to
Resent-Message-ID Mail Message identifier for resent
message
Return-Path Mail Message return path
Received Mail Mail transfer trace information
Disposition-Notification-To
Mail Mailbox for sending disposition
notification
Disposition-Notification-Options
Mail Disposition notification options
Accept-Language Mail Language(s) for auto-responses
Original-Message-ID Mail Original message identifier
PICS-Label Mail PICS rating label
Encoding Mail Message encoding and other
information
List-Archive Mail URL of mailing list archive
List-Help Mail URL for mailing list information
List-ID Mail Mailing list identifier
List-Owner Mail URL for mailing list owner's
mailbox
List-Post Mail URL for mailing list posting
List-Subscribe Mail URL for mailing list subscription
List-Unsubscribe Mail URL for mailing list
unsubscription
Message-Context Mail Type or context of message
DL-Expansion-History
Mail Trace of distribution lists passed
Alternate-Recipient Mail Controls forwarding to alternate
recipients
Original-Encoded-Information-Types
Mail Body part types in message
Content-Return Mail Return content on non-delivery?
Generate-Delivery-Report
Mail Request delivery report generation
Prevent-NonDelivery-Report
Mail Non-delivery report required?
Obsoletes Mail Reference message to be replaced
Supersedes Mail Reference message to be replaced
Content-Identifier Mail Message content identifier
Delivery-Date Mail Message delivery time
Expiry-Date Mail Message expiry time
Expires Mail Message expiry time
Reply-By Mail Time by which a reply is requested
Importance Mail Message importance
Incomplete-Copy Mail Body parts are missing.
Priority Mail Message priority
Sensitivity Mail Message content sensitivity
Language Mail X.400 message content lenguage
Conversion Mail Conversion allowed?
Conversion-With-Loss
Mail Lossy conversion allowed?
Message-Type Mail Message type: delivery report?
Autosubmitted Mail Automatically submitted indicator
Autoforwarded Mail Automatically forwarded indicator
Discarded-X400-IPMS-Extensions
Mail X.400 IPM extensions discarded
Discarded-X400-MTS-Extensions
Mail X.400 MTS extensions discarded
Disclose-Recipients Mail Disclose names of other
recipients?
Deferred-Delivery Mail Deferred delivery information
Latest-Delivery-Time
Mail Latest delivery time requested
Originator-Return-Address
Mail Originator return address
X400-Content-Identifier
Mail Message content identifier
X400-Content-Return Mail Return content on non-delivery?
X400-Content-Type Mail X400 content type
X400-MTS-Identifier Mail X400 MTS-Identifier
X400-Originator Mail X400 Originator
X400-Received Mail X400 Received
X400-Recipients Mail X400 Recipients
X400-Trace Mail X400 Trace
| MailHeaderPermanentRegistry.xml |
- Description:
- Message date and time
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2822[19] (section 3.6.1)
- Related information:
- Specifies the date and time at which the creator of the message indicated that the message was complete and ready to enter the mail delivery system.
- Description:
- Mailbox of message author
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2822[19] (section 3.6.2)
- Related information:
- Specifies the author(s) of the message, that is, the mailbox(es) of the person(s) or system(s) responsible for the writing of the message.
- Description:
- Mailbox of message sender
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2822[19] (section 3.6.2)
- Related information:
- Specifies the mailbox of the agent responsible for the actual transmission of the message.
- Description:
- Mailbox for replies to message
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2822[19] (section 3.6.2)
- Related information:
- When the "Reply-To:" field is present, it indicates the mailbox(es) to which the author of the message suggests that replies be sent.
- Description:
- Primary recipient mailbox
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2822[19] (section 3.6.3)
- Related information:
- Contains the address(es) of the primary recipient(s) of the message.
- Description:
- Carbon-copy recipient mailbox
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2822[19] (section 3.6.3)
- Related information:
- Contains the addresses of others who are to receive the message, though the content of the message may not be directed at them.
- Description:
- Blind-carbon-copy recipient mailbox
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2822[19] (section 3.6.3)
- Related information:
- Contains addresses of recipients of the message whose addresses are not to be revealed to other recipients of the message.
- Description:
- Message identifier
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2822[19] (section 3.6.4)
- Related information:
- Contains a single unique message identifier that refers to a particular version of a particular message. If the message is resent without changes, the original Message-ID is retained.
- Description:
- Identify replied-to message(s)
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2822[19] (section 3.6.4)
- Related information:
- The message identifier(s) of the original message(s) to which the current message is a reply.
- Description:
- Related message identifier(s)
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2822[19] (section 3.6.4)
- Related information:
- The message identifier(s) of other message(s) to which the current message may be related. In RFC2822, the definition was changed to say that this header field contains a list of all Message-IDs of messages in the preceding reply chain.
- Description:
- Topic of message
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2822[19] (section 3.6.5)
- Related information:
- Contains a short string identifying the topic of the message.
- Description:
- Additional comments about the message
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2822[19] (section 3.6.5)
- Related information:
- Contains any additional comments on the text of the body of the message. Warning: Some mailers will not show this field to recipients.
- Description:
- Message key words and/or phrases
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2822[19] (section 3.6.5)
- Related information:
- Contains a comma-separated list of important words and phrases that might be useful for the recipient.
- Description:
- Date and time message is resent
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2822[19] (section 3.6.6)
- Related information:
- Contains the date and time that a message is reintroduced into the message transfer system.
- Description:
- Mailbox of person for whom message is resent
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2822[19] (section 3.6.6)
- Related information:
- Contains the mailbox of the agent who has reintroduced the message into the message transfer system, or on whose behanlf the message has been resent.
- Description:
- Mailbox of person who actually resends the message
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2822[19] (section 3.6.6)
- Related information:
- Contains the mailbox of the agent who has reintroduced the message into the message transfer system, if this is different from the Resent-from value.
- Description:
- Mailbox to which message is resent
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2822[19] (section 3.6.6)
- Related information:
- Contains the mailbox(es) to which the message has been resent.
- Description:
- Mailbox(es) to which message is cc'ed on resend
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2822[19] (section 3.6.6)
- Related information:
- Containes the mailbox(es) to which message is cc'ed on resend
- Description:
- Mailbox(es) to which message is bcc'ed on resend
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2822[19] (section 3.6.6)
- Related information:
- Containes the mailbox(es) to which message is bcc'ed on resend
- Description:
- Resent reply-to
- Applicable protocol:
- Mail[19]
- Status:
- obsolete
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2822[19]
- Related information:
- Resent Reply-to. Defined by RFC 822, obsoleteed by RFC2822.
- Description:
- Message identifier for resent message
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2822[19] (section 3.6.6)
- Related information:
- Contains a message identifier for a resent message
- Description:
- Message return path
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2822[19] (section 3.6.7)
- Related information:
- Return path for message response diagnostics. See also, RFC 2821.
- Description:
- Mail transfer trace information
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2822[19] (section 3.6.7)
- Related information:
- Contains information about receipt of the current message by a mail transfer agent on the transfer path. See also, RFC 2821.
- Description:
- Mailbox for sending disposition notification
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2298[13]
- Related information:
- Indicates that the sender wants a disposition notification when this message is received (read, processed, etc.) by its recipients.
- Description:
- Disposition notification options
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2298[13]
- Related information:
- For optional modifiers on disposition notification requests.
- Description:
- Language(s) for auto-responses
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 3282[22]
- Related information:
- Indicates a language that the message sender requests be used for responses. Accept-language was not designed for email, but has been considered to be useful as input to the generation of automatic replies. Some problems have been noted concerning its use with email, including but not limited to: determination of the email address to which it refers; cost and lack of effective internationalization of email responses; interpretation of language subtags; determining what character set encoding should be used.
- Description:
- Original message identifier
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 3297[23]
- Related information:
- Original message identifier used with resend of message with alternative content format, identifies the original message data to which it corresponds.
- Description:
- PICS rating label
- Applicable protocol:
- Mail[19]
- Status:
- standard
- Author/change controller:
- W3C (mailto:web-human@w3.org)
World Wide Web Consortium- Specification document(s):
- http://www.w3.org/TR/REC-PICS-labels[25]
- Related information:
- Ratings label to control selection (filtering) of messages according to the PICS protocol. Specified for general use with RFC822 message format, with HTTP-specific extensions
- Description:
- Message encoding and other information
- Applicable protocol:
- Mail[19]
- Status:
- experimental
- Author/change controller:
- Albert K. Costanzo (mailto:AL@AKC.COM)
AKC Consulting Inc.- Specification document(s):
- RFC 1505[4]
- Related information:
- Used in several different ways by different mail systems. Some use it for a kind of content-type information, some for encoding and length information, some for a kind of boundary information, some in other ways.
- Description:
- URL of mailing list archive
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2369[14]
- Related information:
- Contains URL to use to browse the archives of the mailing list from which this message was relayed.
- Description:
- URL for mailing list information
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2369[14]
- Related information:
- Contains URL to use to get a information about the mailing list from which this message was relayed.
- Description:
- Mailing list identifier
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2919[21]
- Related information:
- Stores an identification of the mailing list, through which this message was distributed.
- Description:
- URL for mailing list owner's mailbox
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2369[14]
- Related information:
- Contains URL to send e-mail to the owner of the mailing list from which this message was relayed.
- Description:
- URL for mailing list posting
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2369[14]
- Related information:
- Contains URL to use to send contributions to the mailing list from which this message was relayed.
- Description:
- URL for mailing list subscription
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2369[14]
- Related information:
- Contains URL to use to get a subscription to the mailing list from which this message was relayed.
- Description:
- URL for mailing list unsubscription
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2369[14]
- Related information:
- Contains URL to use to unsubscribe the mailing list from which this message was relayed.
- Description:
- Type or context of message
- Applicable protocol:
- Mail[19]
- Status:
- Standards track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC3458[24]
- Related information:
- Provides information about the context and presentation characteristics of a message. Can have the values 'voice-message', 'fax-message', 'pager-message', 'multimedia-message', 'text-message', 'none'.
- Description:
- Trace of distribution lists passed
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- Trace of distribution lists passed. (MIXER X.400 mapping, not for general use.)
- Description:
- Controls forwarding to alternate recipients
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- Controls whether this message may be forwarded to alternate recipients such as a postmaster if delivery is not possible to the intended recipient. Default: Allowed. RFC 2156 (MIXER), not for general use.
- Description:
- Body part types in message
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- Which body part types occur in this message. RFC 2156 (MIXER), not for general use.
- Description:
- Return content on non-delivery?
- Applicable protocol:
- Mail[19]
- Status:
- obsolete
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 1327[2]
- Related information:
- Indicates whether the content of a message is to be returned with non-delivery notifications. Introduced by RFC 1327, and subsequently changed by RFC 2156 to avoid confusion with MIME defined fields.
- Description:
- Request delivery report generation
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- Indicates whether a delivery report is wanted at successful delivery. Default is not to generate such a report. RFC 2156 (MIXER), not for general use.
- Description:
- Non-delivery report required?
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- Indicates whether non-delivery report is wanted on delivery error. Default is to generate such a report. RFC 2156 (MIXER), not for general use.
- Description:
- Reference message to be replaced
- Applicable protocol:
- Mail[19]
- Status:
- obsolete
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 1327[2]
- Related information:
- Reference to a previous message being corrected and replaced. Compare to 'Supersedes:' used in Usenet News. Introduced by RFC 1327, and subsequently renamed by RFC 2156 to 'Supersedes'.
- Description:
- Reference message to be replaced
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- Reference to a previous message being corrected and replaced. Renamed version of obsolete 'Obsoletes' header field. RFC 2156 (MIXER), not for general use.
- Description:
- Message content identifier
- Applicable protocol:
- Mail[19]
- Status:
- obsolete
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 1327[2]
- Related information:
- A text string which identifies the content of a message. Introduced by RFC 1327, and subsequently changed by RFC 2156 to avoid confusion with MIME defined fields. Gateways which reverse map may support the old field.
- Description:
- Message delivery time
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- The time when a message was delivered to its recipient. RFC 2156 (MIXER), not for general use.
- Description:
- Message expiry time
- Applicable protocol:
- Mail[19]
- Status:
- obsolete
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 1327[2]
- Related information:
- Time at which a message loses its validity. Introduced by RFC 1327, and subsequently changed by RFC 2156 to 'Expires:'.
- Description:
- Message expiry time
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- Time at which a message loses its validity. Renamed version of obsolete Expiry-Date header field. RFC 2156 (MIXER), not for general use.
- Description:
- Time by which a reply is requested
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- Latest time at which a reply is requested (not demanded). RFC 2156 (MIXER), not for general use.
- Description:
- Message importance
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- A hint from the originator to the recipients about how important a message is. Values: High, normal or low. Not used to control transmission speed. Proposed for use with RFC 2156 (MIXER) and RFC 2421 (VPIM).
- Description:
- Body parts are missing.
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- Body parts are missing. RFC 2156 (MIXER), not for general use.
- Description:
- Message priority
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- Can be 'normal', 'urgent' or 'non-urgent' and can influence transmission speed and delivery. RFC 2156 (MIXER), not for general use.
- Description:
- Message content sensitivity
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- How sensitive it is to disclose this message to other people than the specified recipients. Values: Personal, private, company confidential. The absence of this header field in messages gatewayed from X.400 indicates that the message is not sensitive. Proposed for use with RFC 2156 (MIXER) and RFC 2421 (VPIM).
- Description:
- X.400 message content lenguage
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- Can include a code for the natural language used in a message, e.g. 'en' for English. See also 'Content-Language'. RFC 2156 (MIXER), not for general use.
- Description:
- Conversion allowed?
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- The body of this message may not be converted from one character set to another. Values: Prohibited and allowed. RFC 2156 (MIXER), not for general use.
- Description:
- Lossy conversion allowed?
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- The body of this message may not be converted from one character set to another if information will be lost. Values: Prohibited and allowed. RFC 2156 (MIXER), not for general use.
- Description:
- Message type: delivery report?
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- Only used with the value 'Delivery Report' to indicates that this is a delivery report gatewayed from X.400. RFC 2156 (MIXER), not for general use.
- Description:
- Automatically submitted indicator
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- Has been automatically submitted. RFC 2156 (MIXER), not for general use.
- Description:
- Automatically forwarded indicator
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- Has been automatically forwarded. RFC 2156 (MIXER), not for general use.
- Description:
- X.400 IPM extensions discarded
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- Can be used in Internet mail to indicate X.400 IPM extensions which could not be mapped to Internet mail format. RFC 2156 (MIXER), not for general use.
- Description:
- X.400 MTS extensions discarded
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- Can be used in Internet mail to indicate X.400 MTS extensions which could not be mapped to Internet mail format. RFC 2156 (MIXER), not for general use.
- Description:
- Disclose names of other recipients?
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- Tells whether recipients are to be told the names of other recipients of the same message. This is primarily an X.400 facility. In X.400, this is an envelope attribute and refers to disclosure of the envelope recipient list. Disclosure of other recipients is in Internet mail done via the To:, cc: and bcc: header fields. Not for general use.
- Description:
- Deferred delivery information
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- Provides information about deferred delivery service to the recipient. RFC 2156 (MIXER), not for general use.
- Description:
- Latest delivery time requested
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- Provides the recipient information about requested delivery, but will not be acted on by the SMTP infrastrucuture. RFC 2156 (MIXER), not for general use.
- Description:
- Originator return address
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- Originator return address. RFC 2156 (MIXER), not for general use.
- Description:
- Message content identifier
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- A text string which identifies the content of a message. Renamed version of obsolete Content-Identifier field. RFC 2156 (MIXER), not for general use.
- Description:
- Return content on non-delivery?
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- Indicates whether the content of a message is to be returned with non-delivery notifications. Renamed version of obsolete Content-Return field. RFC 2156 (MIXER), not for general use.
- Description:
- X400 content type
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- X400 content type. RFC 2156 (MIXER), not for general use.
- Description:
- X400 MTS-Identifier
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- X400 MTS-Identifier. RFC 2156 (MIXER), not for general use.
- Description:
- X400 Originator
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- X400 Originator. RFC 2156 (MIXER), not for general use.
- Description:
- X400 Received
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- X400 Received. RFC 2156 (MIXER), not for general use.
- Description:
- X400 Recipients
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- X400 Recipients. RFC 2156 (MIXER), not for general use.
- Description:
- X400 Trace
- Applicable protocol:
- Mail[19]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2156[11]
- Related information:
- X400 Trace. RFC 2156 (MIXER), not for general use.
Header name Protocol
----------- --------
MIME-Version MIME MIME version number
Content-ID MIME Identify content body part
Content-Description MIME Description of message body part
Content-Transfer-Encoding
MIME Content transfer encoding applied
Content-Type MIME MIME content type
Content-Base MIME Base to be used for resolving
relative URIs within this content
part.
Content-Location MIME URI for retrieving a body part
Content-features MIME Indicates content features of a
MIME body part
Content-Disposition MIME Intended content disposition and
file name
Content-Language MIME Language of message content
Content-Alternative MIME Alternative content available
Content-MD5 MIME MD5 checksum of content
Content-Duration MIME Time duration of content
| MIMEHeaderPermanentRegistry.xml |
- Description:
- MIME version number
- Applicable protocol:
- MIME[7]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2045[7] (section 4)
- Related information:
- An indicator that this message is formatted according to the MIME standard, and an indication of which version of MIME is utilized.
- Description:
- Identify content body part
- Applicable protocol:
- MIME[7]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2045[7] (section 7)
- Related information:
- Specifies a Unique ID for one MIME body part of the content of a message.
- Description:
- Description of message body part
- Applicable protocol:
- MIME[7]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2045[7] (section 8)
- Related information:
- Description of a particular body part of a message, for example a caption for an image body part.
- Description:
- Content transfer encoding applied
- Applicable protocol:
- MIME[7]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2045[7] (section 6)
- Related information:
- Coding method used in a MIME message body part.
- Description:
- MIME content type
- Applicable protocol:
- MIME[7]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2045[7] (section 5)
- Related information:
- Format of content (character set etc.) Note that the values for this header field are defined in different ways in RFC 1049 and in MIME (RFC 2045), look for the 'MIME-version' header field to understand if Content-Type is to be interpreted according to RFC 1049 or according to MIME. The MIME definition should be used in generating mail. RFC 1049 has 'historic' status. RFC 1766 defines a parameter 'difference' to this header field. Various other Content-Type define various additional parameters. For example, the parameter 'charset' is mandatory for all textual Content-Types. See also: RFC 1049, RFC 1123: 5.2.13, RFC 1766: 4.1.
- Description:
- Base to be used for resolving relative URIs within this content part.
- Applicable protocol:
- MIME[7]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2110[9]
- Related information:
- Base to be used for resolving relative URIs within this content part. See also Content-Location. This header was included in the first version of MHTML and HTTP 1.1 but removed in the second version (RFC2557).
- Description:
- URI for retrieving a body part
- Applicable protocol:
- MIME[7]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2557[17]
- Related information:
- URI using which the content of this body-part part was retrieved, might be retrievable, or which otherwise gives a globally unique identification of the content.
- Description:
- Indicates content features of a MIME body part
- Applicable protocol:
- MIME[7]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2912[20] (section 3)
- Related information:
- The 'Content-features:' header can be used to annotate a MIME body part with a media feature expression, to indicate features of the body part content. See also: RFC 2533, RFC 2506, RFC 2045.
- Description:
- Intended content disposition and file name
- Applicable protocol:
- MIME[7]
- Status:
- experimental
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2183[12]
- Related information:
- Whether a MIME body part is to be shown inline or is an attachment; can also indicate a suggested filename for use when saving an attachment to a file.
- Description:
- Language of message content
- Applicable protocol:
- MIME[7]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 3282[22]
- Related information:
- Can include a code for the natural language used in a message, e.g. 'en' for English. Can also contain a list of languages for a message containing more than one language.
- Description:
- Alternative content available
- Applicable protocol:
- MIME[7]
- Status:
- work-in-progress
- Author/change controller:
- Graham Klyne (mailto:GK-IETF@ninebynine.org)
Nine by Nine- Specification document(s):
- RFC 3297[23]
- Related information:
- Information about the media features of alternative content formats available for the current message.
- Description:
- MD5 checksum of content
- Applicable protocol:
- MIME[7]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 1864[6]
- Related information:
- Checksum of content to ensure that it has not been modified.
- Description:
- Time duration of content
- Applicable protocol:
- MIME[7]
- Status:
- standards-track
- Author/change controller:
- IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force- Specification document(s):
- RFC 2424[16]
- Related information:
- Time duration of body part content, in seconds (e.g. for audio message).
| TOC |
This specification provides initial registrations of mail and MIME headers in the "Permanent Message Header Field Registry", defined by Registration procedures for message header fields[1].
| TOC |
No security considerations are introduced by this specification beyond those already inherent in the use of message headers.
| TOC |
Most of the information in this document has been derived from Jacob Palme's work in RFC 2076[26] and subsequent updates [27].
The authors also gratefully acknowledge the contributions of: Mark Nottingham, Bruce Lilly, [[[...]]]
| TOC |
| TOC |
| [26] | Palme, J., "Common Internet Message Headers", RFC 2076, February 1997. |
| [27] | Palme, J., "Common Internet Message Header Fields", Internet draft draft-palme-mailext-headers-06, November 2001. |
| TOC |
| Graham Klyne | |
| Nine by Nine | |
| UK | |
| EMail: | GK-IETF@ninebynine.org |
| URI: | http://www.ninebynine.net/ |
| Jacob Palme | |
| Stockholm University/KTH | |
| Forum 100 | |
| Kista S-164 40 | |
| Sweden | |
| Phone: | +46-8-16 16 67 |
| EMail: | jpalme@dsv.su.se |
| TOC |
[[[Please remove this section on final publication]]]
- 03c 13-Apr-2004:
- Added Accept-Language header, with some warning text concerning its use with email.
- Removed Originator headere, since it is not used as a mail message header.
- Fix up report generator error in author/change controller handling.
- 03b 06-Apr-2004:
- Using a new version of the RDF-to-documentation generator for registry entry data.
- Revised format of registry entries to avoid some duplication of document and author details.
- Added documents referenced by the regsitration entries to the references section, and added citations to the entries themselves.
- 03a 15-Mar-2004:
- Added and revised header details, per comments from Bruce Lilly.
- 02d 19-Feb-2004:
- Incorporated small changes to specific header field descriptions, suggested by Jacob.
- 02c 18-Feb-2004:
- Separated Mail and MIME header fields.
- Corrected specification reference for MIXER headers (RFC 2156).
- Changed applicable protocol for MIME header fields.
- Other smaller corrections.
- 02b 17-Feb-2004:
- Removed provisional mail header registrations from this document.
- 02a 05-Aug-2002:
- Added Jacob Palme as co-editor.
- 01c 05-Jun-2002:
- Minor editorial.
- 01b 10-May-2002:
- Updated some contact information.
- Regenerated registry tables with revised software.
- 01a 08-May-2002:
- Revised change controller information in line with registry specification.
- Cleaned up some table layout.
- 00c 05-May-2002:
- Added data for permanent and provisional registries.
- 00b 01-May-2002:
- Revised form of registry entry content. (Auto-generated from RDF data.)
- 00a 22-Jan-2002:
- Document initially created.
| TOC |
[[[Please remove this section on final publication]]]
| TOC |
The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.
Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Funding for the RFC Editor function is currently provided by the Internet Society.