Cite this STD: TXTSTD 10 contains the following RFCs:
|RFC 821, STD 10||ASCII, PDF||Simple Mail Transfer Protocol||J. Postel||August 1982||Obsoletes RFC 788, Obsoleted by RFC 2821||Internet Standard|
|RFC 974, STD 10||ASCII, PDF||Mail routing and the domain system||C. Partridge||January 1986||Obsoleted by RFC 2821||Historic (was published as Internet Standard )|
|RFC 1869, STD 10||ASCII, PDF||SMTP Service Extensions||J. Klensin, N. Freed, M. Rose, E. Stefferud, D. Crocker||November 1995||Obsoletes RFC 1651, Obsoleted by RFC 2821||Internet Standard|
|RFC 1870, STD 10||ASCII, PDF||SMTP Service Extension for Message Size Declaration||J. Klensin, N. Freed, K. Moore||November 1995||Obsoletes RFC 1653||Internet Standard|
Abstract of RFC 821
The objective of Simple Mail Transfer Protocol (SMTP) is to transfer mail reliably and efficiently. SMTP is independent of the particular transmission subsystem and requires only a reliable ordered data stream channel. Obsoletes RFC 788, 780, and 772.
Abstract of RFC 974
This RFC presents a description of how mail systems on the Internet are expected to route messages based on information from the domain system. This involves a discussion of how mailers interpret MX RRs, which are used for message routing.
Abstract of RFC 1869
This memo defines a framework for extending the SMTP service by defining a means whereby a server SMTP can inform a client SMTP as to the service extensions it supports. [STANDARDS-TRACK]
Abstract of RFC 1870
This memo defines an extension to the SMTP service whereby an SMTP client and server may interact to give the server an opportunity to decline to accept a message (perhaps temporarily) based on the client's estimate of the message size. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 4844.