Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Notational conventions ................................... It contains no specification of the information in the envelope.Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Copyright Notice Copyright (C) The Internet Society (2001). Abstract This standard specifies a syntax for text messages that are sent between computer users, within the framework of "electronic mail" messages. Scope .................................................... However, some message systems may use information from the contents to create the envelope.This standard supersedes the one specified in Request For Comments (RFC) 822, "Standard for the Format of ARPA Internet Text Messages", updating it to reflect current practice and incorporating incremental changes that were specified in other RFCs. Introduction ............................................... It is intended that this standard facilitate the acquisition of such information by programs.

Long Header Fields ..................................... Notices ...........................................50 Full Copyright Statement ......................................51 This standard specifies a syntax for text messages that are sent between computer users, within the framework of "electronic mail" messages.

Body ..................................................... Differences from earlier standards ................49 Appendix C.

Syntax ..................................................... Obsoleted forms ..........................................47 A.6.1. Obsolete addressing ....................................48 A.6.2. Obsolete dates .........................................48 A.6.3. Obsolete white space and comments ......................48 Appendix B.

Line Length Limits ..................................... There are several extensions published, such as the MIME document series [RFC2045, RFC2046, RFC2049], which describe mechanisms for the transmission of such data through electronic mail, either by extending the syntax provided here or by structuring such messages to conform to this syntax.

Header Fields ............................................ In particular, it makes no provision for the transmission of images, audio, or other sorts of structured data in electronic mail messages.

Unstructured Header Field Bodies ....................... This standard specifies a syntax only for text messages.

Structured Header Field Bodies ......................... This standard supersedes the one specified in Request For Comments (RFC) 822, "Standard for the Format of ARPA Internet Text Messages" [RFC822], updating it to reflect current practice and incorporating incremental changes that were specified in other RFCs [STD3].

Syntactic notation ..................................... (See [RFC2821] for a discussion of the envelope.) The contents comprise the object to be delivered to the recipient.

Structure of this document ............................... The envelope contains whatever information is needed to accomplish transmission and delivery.

Lexical Analysis of Messages ............................... In the context of electronic mail, messages are viewed as having an envelope and contents.

General Description ...................................... Those mechanisms are outside of the scope of this standard.