Connected: An Internet Encyclopedia
RFC 821 - Too Many Recipients Scenario

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 821
Up: APPENDIX F: Scenarios
Prev: Forwarding Scenarios
Next: GLOSSARY

### Too Many Recipients Scenario

             R: 220 BERKELEY.ARPA Simple Mail Transfer Service Ready
             S: HELO USC-ISIF.ARPA
             R: 250 BERKELEY.ARPA

             S: MAIL FROM:<Postel@USC-ISIF.ARPA>
             R: 250 OK

             S: RCPT TO:<fabry@BERKELEY.ARPA>
             R: 250 OK

             S: RCPT TO:<eric@BERKELEY.ARPA>
             R: 552 Recipient storage full, try again in another transaction

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

             S: MAIL FROM:<Postel@USC-ISIF.ARPA>
             R: 250 OK

             S: RCPT TO:<eric@BERKELEY.ARPA>
             R: 250 OK

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

             S: QUIT
             R: 221 BERKELEY.ARPA Service closing transmission channel

                                  Scenario 10

Note that a real implementation must handle many recipients as specified in Section 4.5.3.

Next: GLOSSARY

Connected: An Internet Encyclopedia
RFC 821 - Too Many Recipients Scenario