| TOC |
|
By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668.
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 April 27, 2005.
Copyright (C) The Internet Society (2004). All Rights Reserved.
This document requests IANA registration of several provisional mail message header fields, per RFC 3864.
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>.
1.
Introduction
2.
Registration templates
2.1
Provisional mail header field registrations
2.1.1
Header field: Apparently-To
2.1.2
Header field: Approved-By
2.1.3
Header field: Fax
2.1.4
Header field: Telefax
2.1.5
Header field: For-Approval
2.1.6
Header field: For-Comment
2.1.7
Header field: For-Handling
2.1.8
Header field: Mail-System-Version
2.1.9
Header field: Mailer
2.1.10
Header field: Originating-Client
2.1.11
Header field: X-Mailer
2.1.12
Header field: X-Newsreader
2.1.13
Header field: X-MimeOLE
2.1.14
Header field: User-Agent
2.1.15
Header field: Originator-Info
2.1.16
Header field: Phone
2.1.17
Header field: X-Envelope-From
2.1.18
Header field: Envelope-To
2.1.19
Header field: X-Envelope-To
2.1.20
Header field: X-Face
2.1.21
Header field: X-RCPT-TO
2.1.22
Header field: X-Sender
2.1.23
Header field: X-X-Sender
2.1.24
Header field: Posted-To
2.1.25
Header field: X-Admin
2.1.26
Header field: Errors-To
2.1.27
Header field: Return-Receipt-To
2.1.28
Header field: Read-Receipt-To
2.1.29
Header field: X-Confirm-reading-to
2.1.30
Header field: Return-Receipt-Requested
2.1.31
Header field: Register-Mail-Reply-Requested-By
2.1.32
Header field: Abuse-Reports-To
2.1.33
Header field: X-Complaints-To
2.1.34
Header field: X-Report-Abuse-To
2.1.35
Header field: Content-Alias
2.1.36
Header field: Delivered-To
2.1.37
Header field: X-Loop
2.1.38
Header field: Translated-By
2.1.39
Header field: Translation-Of
2.1.40
Header field: X-UIDL
2.1.41
Header field: X-URI
2.1.42
Header field: X-URL
2.1.43
Header field: X-IMAP
2.1.44
Header field: X-OriginalArrivalTime
2.1.45
Header field: Precedence
2.1.46
Header field: X-MSMail-Priority
2.1.47
Header field: X-Priority
2.1.48
Header field: Content-Length
2.1.49
Header field: Content-Conversion
2.1.50
Header field: Content-Class
2.1.51
Header field: Content-SGML-Entity
2.1.52
Header field: X-MIME-Autoconverted
2.1.53
Header field: List-Digest
2.1.54
Header field: Mailing-List
2.1.55
Header field: X-Mailing-List
2.1.56
Header field: List-Software
2.1.57
Header field: List-URL
2.1.58
Header field: X-Listserver
2.1.59
Header field: X-List-Host
2.1.60
Header field: Fcc
2.1.61
Header field: Speech-Act
2.1.62
Header field: Status
2.1.63
Header field: X-No-Archive
2.1.64
Header field: X-Request-PGP
3.
IANA considerations
4.
Security considerations
5.
Acknowledgements
§.
Normative references
§.
Informative references
§
Authors' Addresses
A.
Revision history
A.1
draft-klyne-hdrreg-prov-mail-00
B.
TODO:
§
Intellectual Property and Copyright Statements
| TOC |
This document defines IANA registration templates for a number of provisional mail message header fields, per Registration Procedures for Message Header FieldsKlyne, G., Nottingham, M. and J. Mogul, Registration Procedures for Message Header Fields, September 2004.[2].
The message header fields whose registration is requested by this document have not, at the time of this registration, been agreed by the IETF as appropriate for standardization, and their inclusion in the provisional message header registry is not an indication that they will be considered for standardization. The purpose of such registration is to make existence of their proposal known to email sofware and standards devlopers. No assurance is hereby given that using any of these headers in actual email messages will be safe and non-detrimental.
A key purpose of this document is to transfer information about message header fields contained in Jacob Palme's long running work (cf. [3]Palme, J., Common Internet Message Headers, February 1997., [4]Palme, J., Common Internet Message Header Fields, November 2001., and elsewhere) to the IANA provisional registry created by RFC 3864Klyne, G., Nottingham, M. and J. Mogul, Registration Procedures for Message Header Fields, September 2004.[2] where continued maintenance of this information can be a shared community effort. The provisional registry entries requested by this document are not final, and anyone with better information is encouraged to submit updated registry entries.
[[[At the time of writing, the information available concerning some of the header fields mentioned here is incomplete. In some cases, the author and specification document is unknown, which is not an entirely satisfactory state of affairs. We encourage anyone with more detailed information to request its inclusion in the registry, either by commenting on this draft while in its review stages, or by submitting new and/or updated registration templates for the registered header field names.]]]
The main body of this document is automatically generated from a Semantic Web data format (RDF/N3).
| TOC |
Header field provisional registry entries are summarized in tabular form for convenience of reference, and presented in full in the following sections.
Header name Protocol Status
----------- -------- ------
Apparently-To Mail provisional
Approved-By Mail provisional
Fax Mail provisional
Telefax Mail provisional
For-Approval Mail provisional
For-Comment Mail provisional
For-Handling Mail provisional
Mail-System-Version Mail provisional
Mailer Mail provisional
Originating-Client Mail provisional
X-Mailer Mail provisional
X-Newsreader Mail provisional
X-MimeOLE Mail provisional
User-Agent Mail provisional
Originator-Info Mail provisional
Phone Mail provisional
X-Envelope-From Mail provisional
Envelope-To Mail provisional
X-Envelope-To Mail provisional
X-Face Mail provisional
X-RCPT-TO Mail provisional
X-Sender Mail provisional
X-X-Sender Mail provisional
Posted-To Mail provisional
X-Admin Mail provisional
Errors-To Mail provisional
Return-Receipt-To Mail provisional
Read-Receipt-To Mail provisional
X-Confirm-reading-to Mail provisional
Return-Receipt-Requested Mail provisional
Register-Mail-Reply-Requested-By
Mail provisional
Abuse-Reports-To Mail provisional
X-Complaints-To Mail provisional
X-Report-Abuse-To Mail provisional
Content-Alias Mail provisional
Delivered-To Mail provisional
X-Loop Mail provisional
Translated-By Mail provisional
Translation-Of Mail provisional
X-UIDL Mail provisional
X-URI Mail provisional
X-URL Mail provisional
X-IMAP Mail provisional
X-OriginalArrivalTime Mail provisional
Precedence Mail provisional
X-MSMail-Priority Mail provisional
X-Priority Mail provisional
Content-Length Mail provisional
Content-Conversion Mail provisional
Content-Class Mail provisional
Content-SGML-Entity Mail provisional
X-MIME-Autoconverted Mail provisional
List-Digest Mail provisional
Mailing-List Mail provisional
X-Mailing-List Mail provisional
List-Software Mail provisional
List-URL Mail provisional
X-Listserver Mail provisional
X-List-Host Mail provisional
Fcc Mail provisional
Speech-Act Mail provisional
Status Mail provisional
X-No-Archive Mail provisional
X-Request-PGP Mail provisional
- Description:
- Envelope recipients inserted my MTA
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Inserted by Sendmail when there is no 'To:' recipient in the original message, listing recipients derived from the envelope into the message heading. This behavior is not quite proper, MTAs should not modify headings (except inserting Received lines), and it can in some cases cause Bcc recipients to be wrongly divulged to non-Bcc recipients. Discouraged, mentioned in RFC 1211.
- With some versions of Sendmail, inserting "undisclosed recipients:;" into the "To:" header field will prevent Sendmail from doing this. Some mailers know this and automatically add this header to messages having only Bcc recipients.
- Description:
- Mailing list moderator who has approved message
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Name of the moderator of a mailing list, who has approved this message for distribution to the members of the list. Non-standard, used by some mailing list expansion systems.
- Description:
- Fax number of the originator
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Fax number of the originator.
- Description:
- Fax number of the originator
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Fax number of the originator.
- Description:
- Recipients for approval of this message
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Primary recipients, who are requested to approve the information in this message or its attachments.
- Description:
- Recipients for comment on this message
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Primary recipients, who are requested to comment on the information in this message or its attachments.
- Description:
- Primary recipients for handling this message
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Primary recipients, who are requested to handle the information in this message or its attachments.
- Description:
- Information about originating client software
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Information about the client software of the originator.
- Description:
- Information about originating client software
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Information about the client software of the originator.
- Description:
- Information about originating client software
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Information about the client software of the originator.
- Description:
- Information about originating client software
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Information about the client software of the originator.
- Description:
- Information about originating client software
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Information about the client software of the originator.
- Description:
- Information about originating client software
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Information about the client software of the originator.
- Description:
- Information about originating client software
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Information about the client software of the originator.
- Description:
- Originator authentication information
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-newman-msgheader-originfoNewman, C., Originator-Info Message Header field, May 1998.[5]
- Related information:
- Contains information about the authentication of the originator in a format which is not easily used to send email to, to avoid the problems with 'Sender' and 'X-Sender'.
- Description:
- Phone number of the originator.
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Phone number of the originator.
- Description:
- Mail envelope sender
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- If the sender in the envelope (SMTP 'MAIL FROM') is not the same as the senders in the 'From' or 'Sender' header fields, some mail servers add this as an aid to clients which would otherwise not be able to display this information.
- Description:
- Mail envelope recipient
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- If the recipient in the envelope (SMTP 'RCPT TO') is not included in the CC list, some mail servers add this header field as an aid to clients which would otherwise not be able to display the envelope recipients.
- Description:
- Mail envelope recipient
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- If the recipient in the envelope (SMTP 'RCPT TO') is not included in the CC list, some mail servers add this header field as an aid to clients which would otherwise not be able to display the envelope recipients.
- Description:
- Picture of the sender
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- 48x48 bitmap with picture of the sender of this message.
- Description:
- Mail envelope recipient
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Mail header field indication of the of the SMTP envelope recipient for this message.
- Description:
- Tentative message sender
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Some mail software expects 'Sender:' to be an e-mail address to which mail can be sent, and use it as the target for certain kinds of adminstrative message. However, some mail senders use an authenticated sender identifier, which looks like an email address but may not be able to actually receive mail. Because of this, some mail software puts the authenticated sender identifier into an X-sender header field instead of a Sender header field, to indicate that the address may be unable to receive e-mail. See also 'X-X-Sender'.
- Another use of 'X-Sender:' is that some e-mail software, which wants to insert a 'Sender:' header, will first change an existing 'Sender:' header to 'X-Sender'. This use is actually often similar to that described above, since the new 'Sender:' is added because it is better authenticated than the old value.
- Description:
- Extra-tentative message sender
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Even though some systems put the POP or IMAP account name into the 'X-Sender:' instead of the Sender header field, some mail software tries to send to the 'X-Sender:' too. To stop this, some systems have begun to use 'X-X-Sender:' to indicate an authentication of the sender which might not be useable to send e-mail to. See also 'Originator-Info:'.
- Description:
- Nesgroup to which message was sent
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- When a message is sent both to netnews and e-mail, this header is used in the e-mail version of the message to indicate which newsgroup it was sent to. This header thus contains the same information as the 'Newsgroups:' header in the netnews version of the message.
- Description:
- Submission server administrator mailbox
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- E-mail address of administrator of a server, through which this message was submitted.
- Description:
- Address for notifications to be sent
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Address to which notifications are to be sent and a request to get delivery notifications. Internet standards recommend, however, the use of MAIL FROM and Return-Path, not Errors-To, for where delivery notifications are to be sent. Non-standard, discouraged, may be widely used.
- Description:
- Address for notifications to be sent
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Address to which notifications are to be sent and a request to get delivery notifications. Internet standards recommend, however, the use of MAIL FROM and Return-Path, not Errors-To, for where delivery notifications are to be sent. Non-standard, discouraged, may be widely used.
- Description:
- Address for notifications to be sent
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Address to which notifications are to be sent and a request to get delivery notifications. Internet standards recommend, however, the use of MAIL FROM and Return-Path, not Errors-To, for where delivery notifications are to be sent. Non-standard, discouraged, may be widely used.
- Description:
- Address for notifications to be sent
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Address to which notifications are to be sent and a request to get delivery notifications. Internet standards recommend, however, the use of MAIL FROM and Return-Path, not Errors-To, for where delivery notifications are to be sent. Non-standard, discouraged, may be widely used.
- Description:
- Address for notifications to be sent
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Address to which notifications are to be sent and a request to get delivery notifications. Internet standards recommend, however, the use of MAIL FROM and Return-Path, not Errors-To, for where delivery notifications are to be sent. Non-standard, discouraged, may be widely used.
- Description:
- Address for notifications to be sent
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Address to which notifications are to be sent and a request to get delivery notifications. Internet standards recommend, however, the use of MAIL FROM and Return-Path, not Errors-To, for where delivery notifications are to be sent. Non-standard, discouraged, may be widely used.
- Description:
- Mailbox for reporting abuse
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Indicates where to send complaints if you get a message which you think is against the laws or rules.
- Description:
- Mailbox for reporting abuse
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Indicates where to send complaints if you get a message which you think is against the laws or rules.
- Description:
- Mailbox for reporting abuse
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Indicates where to send complaints if you get a message which you think is against the laws or rules.
- Description:
- Alternatice to Content-Location URI
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Used in addition to Content-Location if this content part can be retrieved through more than one URI. Only one of them is allowed in the Content-Location, the other can be specified in Content-Alias.
- Description:
- Message loop detection
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Used by some automatic services (mainly MLMs and autoresponders) for the purpose of loop detection. The service adds the Delivered-To header to outgoing messages, with its e-mail address as a value, and discards incoming messages which already have it.
- Description:
- Message loop detection
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Used by some automatic services (mainly MLMs and autoresponders) for the purpose of loop detection. The service adds the Delivered-To header to outgoing messages, with its e-mail address as a value, and discards incoming messages which already have it.
- Description:
- Mailbox of translator
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Mailbox of the person or agent who made the translation.
- Description:
- Reference source of translation
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Reference to the Message-ID of a message, of which the current message is a translation.
- Description:
- Message identifier within mailstore
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Unique identifier for a message, local to a particular local mailbox store. The UIDL identifier is defined in the POP3 standard, but not the 'X-UIDL:' header.
- Description:
- URI of body part content
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Similar usage as 'X-URL', but may indicate any URI, not just a URL.
- Description:
- Location of body part content
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Sometimes used with the same meaning as 'Content-Location:', sometimes to indicate the web home page of the sender or of his organisation.
- Description:
- IMAP UID
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- The UID, as defined in the IMAP standard. Only used in internal mailbox storage in some mail systems, should never be visible to a user.
- Description:
- Time message was submitted
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Time when this message was delivered into the message transport system (usually the same time as in the last 'Received:' header)
- Description:
- Message precedence indicator
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Sometimes used as a priority value which can influence transmission speed and delivery. Common values are 'bulk' and 'first-class'. Other uses is to control automatic replies and to control return-of-content facilities, and to stop mailing list loops. Non-standard, controversial, widely used.
- Description:
- Yet another priority indication.
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Yet another priority indication.
- Description:
- Message priority
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Values: 1 (Highest), 2 (High), 3 (Normal), 4 (Low), 5 (Lowest). 3 (Normal) is default if the field is omitted. See also the Eudora Pro Macintosh User Manual, QUALCOMM Inc
- Description:
- Size in bytes of body part
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Inserted by certain mailers to indicate the size in bytes of the message text. This is part of a format some mailers use when showing a message to its users, and this header field should not be used when sending a message through the net. The use of this header field in transmission of a message can cause several robustness and interoperability problems.
- Description:
- Variant of 'Conversion:'
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Non-standard variant of 'Conversion:' with the same values.
- Description:
- Hierarchical content classification
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Type information of the content in some class hierarchy. Class hierarchies are commonly used to classify data structures in software development.
- Description:
- SGML entity information
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Information from the SGML entity declaration corresponding to the entity contained in the body of the body part.
- Description:
- In-transit message conversion information
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Information about conversion of this message on the path from sender to recipient, such as conversion between MIME encoding formats.
- Description:
- URL for mailing list digest subscription
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- URL to use to get a subscription to the digest version of a mailing list from which this message was relayed.
- Description:
- Mailing list information
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Non-standard precursors to List-ID and List-Post.
- Description:
- Mailing list information
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Non-standard precursors to List-ID and List-Post.
- Description:
- Mailing list software information
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Information about the software used in a mailing list expander through which this message has passed. Non-standard, has been considered for inclusion in RFC2369.
- Description:
- URL for mailing list information
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Contains URL where information of various kinds about the mailing list from which this message was relayed.
- Description:
- List server software information
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Information about the server and software used in a mailing list expander through which this message has passed. Warning: 'Listserv' is a trademark and should not be used for other than the 'Listserv' product. Use, instead the 'List-Software' header field. Non-standard. Recommended to use 'List-Software' instead.
- Description:
- List server software information
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Information about the server and software used in a mailing list expander through which this message has passed. Warning: 'Listserv' is a trademark and should not be used for other than the 'Listserv' product. Use, instead the 'List-Software' header field. Non-standard. Recommended to use 'List-Software' instead.
- Description:
- File for copy of message
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Name of a file or folder in which a copy of this message is stored.
- Description:
- Speech act categorization of message
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Speech act categoriztion of a message. Examples of speech acts are Question, Idea, More, Promise, Sad, Happy, Angry, Summary, Decision.
- Description:
- Message status in delivery system
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- This field is used by some mail delivery systems to indicate the status of delivery for this message when stored. Common values of this field are:
- U
- message is not downloaded and not deleted.
- R
- message is read or downloaded.
- O
- message is old but not deleted.
- D
- to be deleted.
- N
- new (a new message also sometimes is distinguished by not having any 'Status:' header field).
Combinations of these characters can occur, such as 'Status: OR' to indicate that a message is downloaded but not deleted. Non-standard, should never appear in mail in transit.
- Description:
- Do not archive publicly
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Unknown
- Specification document(s):
- draft-palme-mailext-headersPalme, J., Common Internet Message Header Fields, November 2001.[4]
- Related information:
- Do not archive this message in publicly available archives.
- Description:
- Request for PGP public key
- Applicable protocol:
- MailResnick, P., Internet Message Format, April 2001.[1]
- Status:
- provisional
- Author/change controller:
- Werner Koch (mailto:wk@gnupg.org)
- Specification document(s):
- unknown
- Related information:
- 'X-Request-PGP: <url>' is a request that the sender wants the recipient to send him the PGP open key for <url>.
| TOC |
This document requests the registration of message header fields listed in Section 2.1, and subsections, in the Provisional Message Header Field Registry, which is defined by the document Registration Procedures for Message Header FieldsKlyne, G., Nottingham, M. and J. Mogul, Registration Procedures for Message Header Fields, September 2004.[2].
| TOC |
No security considerations are introduced by this registration document beyond those already inherent in use of the mail message header fields referenced.
In most cases, the message header fields mentioned in this doicument have not been subjected to IETF or community review, and their use should not be assumed to be without risk.
| TOC |
Most of the information in this document has been derived from Jacob Palme's work in RFC 2076Palme, J., Common Internet Message Headers, February 1997.[3] and subsequent updates [4]Palme, J., Common Internet Message Header Fields, November 2001..
The authors also gratefully acknowledge contributions and constructive input from: Bruce Lily.
| TOC |
| TOC |
| [1] | Resnick, P., "Internet Message Format", RFC 2822, April 2001. |
| [2] | Klyne, G., Nottingham, M. and J. Mogul, "Registration Procedures for Message Header Fields", BCP 90, RFC 3864, September 2004. |
| TOC |
| [3] | Palme, J., "Common Internet Message Headers", RFC 2076, February 1997. |
| [4] | Palme, J., "Common Internet Message Header Fields", Internet draft draft-palme-mailext-headers-08, November 2001. |
| [5] | Newman, C., "Originator-Info Message Header field", Internet draft (expired) draft-newman-msgheader-originfo-05, May 1998. |
| 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 |
| Fax: | +46-8-783 08 29 |
| EMail: | jpalme@dsv.su.se |
| TOC |
[[[Please remove this section on final publication]]]
- 00a 20-Oct-2004:
- Document initially created.
- 00b 27-Oct-2004:
- Updated some header field details.
| TOC |
[[[Please remove this section on final publication]]]
| TOC |
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights 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; nor does it represent that it has made any independent effort to identify any such rights. Information on the IETF's procedures with respect to rights in IETF Documents can be found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat 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 implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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.
Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
Funding for the RFC Editor function is currently provided by the Internet Society.