Connected: An Internet Encyclopedia
RFC 821 - 3.1. MAIL

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 821
Up: 3. THE SMTP PROCEDURES
Prev: 3. THE SMTP PROCEDURES
Next: 3.2. FORWARDING

### 3.1. MAIL

There are three steps to SMTP mail transactions. The transaction is started with a MAIL command which gives the sender identification. A series of one or more RCPT commands follows giving the receiver information. Then a DATA command gives the mail data. And finally, the end of mail data indicator confirms the transaction.

The first step in the procedure is the MAIL command. The <reverse-path> contains the source mailbox.

                MAIL <SP> FROM:<reverse-path> <CRLF>

This command tells the SMTP-receiver that a new mail transaction is starting and to reset all its state tables and buffers, including any recipients or mail data. It gives the reverse-path which can be used to report errors. If accepted, the receiver-SMTP returns a 250 OK reply.

The <reverse-path> can contain more than just a mailbox. The <reverse-path> is a reverse source routing list of hosts and source mailbox. The first host in the <reverse-path> should be the host sending this command.

The second step in the procedure is the RCPT command.

                RCPT <SP> TO:<forward-path> <CRLF>

This command gives a forward-path identifying one recipient. If accepted, the receiver-SMTP returns a 250 OK reply, and stores the forward-path. If the recipient is unknown the receiver-SMTP returns a 550 Failure reply. This second step of the procedure can be repeated any number of times.

The <forward-path> can contain more than just a mailbox. The <forward-path> is a source routing list of hosts and the destination mailbox. The first host in the <forward-path> should be the host receiving this command.

The third step in the procedure is the DATA command.

                DATA <CRLF>

If accepted, the receiver-SMTP returns a 354 Intermediate reply and considers all succeeding lines to be the message text. When the end of text is received and stored the SMTP-receiver sends a 250 OK reply.

Since the mail data is sent on the transmission channel the end of the mail data must be indicated so that the command and reply dialog can be resumed. SMTP indicates the end of the mail data by sending a line containing only a period. A transparency procedure is used to prevent this from interfering with the user's text (see Section 4.5.2).

Please note that the mail data includes the memo header items such as Date, Subject, To, Cc, From [2].

The end of mail data indicator also confirms the mail transaction and tells the receiver-SMTP to now process the stored recipients and mail data. If accepted, the receiver-SMTP returns a 250 OK reply. The DATA command should fail only if the mail transaction was incomplete (for example, no recipients), or if resources are not available.

The above procedure is an example of a mail transaction. These commands must be used only in the order discussed above. Example 1 (below) illustrates the use of these commands in a mail transaction.

                         Example of the SMTP Procedure

             This SMTP example shows mail sent by Smith at host Alpha.ARPA,
             to Jones, Green, and Brown at host Beta.ARPA.  Here we assume
             that host Alpha contacts host Beta directly.

                S: MAIL FROM:<Smith@Alpha.ARPA>
                R: 250 OK

                S: RCPT TO:<Jones@Beta.ARPA>
                R: 250 OK

                S: RCPT TO:<Green@Beta.ARPA>
                R: 550 No such user here

                S: RCPT TO:<Brown@Beta.ARPA>
                R: 250 OK

                S: DATA
                R: 354 Start mail input; end with <CRLF>.<CRLF>
                S: Blah blah blah...
                S: ...etc. etc. etc.
                S: <CRLF>.<CRLF>
                R: 250 OK

             The mail has now been accepted for Jones and Brown.  Green did
             not have a mailbox at host Beta.

                                   Example 1

Next: 3.2. FORWARDING

Connected: An Internet Encyclopedia
RFC 821 - 3.1. MAIL