RFC 2076 (rfc2076) - Page 3 of 27
Common Internet Message Headers
Alternative Format: Original Text Document
RFC 2076 Internet Message Headers February 1997
It is my intention to continue updating this document after its
publication as an RFC. The latest version, which may be more up-to-
date (but also less fully checked out) will be kept available for
downloading from URL
http://www.dsv.su.se/~jpalme/ietf-mail-attributes.pdf.
Please e-mail me (Jacob Palme [email protected]>) if you have noted
headers which should be included in this memo but are not.
2. Use of gatewaying headers
RFC 1327 defines a number of new headers in Internet mail, which are
defined to map headers which X.400 has but which were previously not
standardized in Internet mail. The fact that a header occurs in RFC
1327 indicates that it is recommended for use in gatewaying messages
between X.400 and Internet mail, but does not mean that the header is
recommended for messages wholly within Internet mail. Some of these
headers may eventually see widespread implementation and use in
Internet mail, but at the time of this writing (1996) they are not
widely implemented or used.
Headers defined only in RFC 1036 for use in Usenet News sometimes
appear in mail messages, either because the messages have been
gatewayed from Usenet News to e-mail, or because the messages were
written in combined clients supporting both e-mail and Usenet News in
the same client. These headers are not standardized for use in
Internet e-mail and should be handled with caution by e-mail agents.
3. Table of headers
3.1 Phrases used in the tables
"not for general Used to mark headers which are defined in RFC
usage" 1327 for use in messages from or to Internet
mail/X.400 gateways. These headers have not
been standardized for general usage in the
exchange of messages between Internet mail-
based systems.
Palme Informational
