RFC 2033: Local Mail Transfer Protocol
In plain English — editorial summary, not part of the RFC
SMTP [SMTP] [HOST-REQ] and its service extensions [ESMTP] provide a mechanism for transferring mail reliably and efficiently. The design of the SMTP protocol effectively requires the server to manage a mail delivery queue. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2033
- Published
- October 1996
- Authors
- J. Myers
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1893Enhanced Mail System Status CodesObsoleted
January 1996
- RFC 2034SMTP Service Extension for Returning Enhanced Error CodesCurrent
October 1996
- RFC 1985SMTP Service Extension for Remote Message Queue StartingCurrent
August 1996
- RFC 2197SMTP Service Extension for Command PipeliningObsoleted
September 1997
- RFC 1652SMTP Service Extension for 8bit-MIMEtransportObsoleted
July 1994
- RFC 2442The Batch SMTP Media TypeCurrent
November 1998
- RFC 2487SMTP Service Extension for Secure SMTP over TLSObsoleted
January 1999
- RFC 2505Anti-Spam Recommendations for SMTP MTAsCurrent
February 1999
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?