Skip to main content

Requirements for Internet Mail Transport Agents

Document Type Expired Internet-Draft (mailext WG)
Expired & archived
Authors Ned Freed , Keith Moore , Dr. John C. Klensin , Jeroen Houttuin
Last updated 1995-03-27 (Latest revision 1995-01-25)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Expired
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


This document reflects apparent ambiguities in RFC 821 that remain after the clarifications in RFC 1123. It also includes some material from RFC 1123 that appeared to need amplification. These have been identified in multiple ways, mostly by tracking flaming on the header-people list and problems of unusual readings or interpretations that have turned up as the SMTP extensions have been deployed. It is important to note that everything here is in response to some identified confusion or bad behavior, not just paranoia. Although SMTP was designed as a mail transport and delivery protocol, this specification also contains information that is important to its use as a 'mail posting' protocol, as recommended for POP3 [RFC-POP3] and IMAP4 [RFC-IMAP4]. Except when the historical terminology is necessary for clarity, this document uses the current 'client' and 'server' terminology to identify the sending and receiving SMTP processes, respectively. A companion document discusses mail bodies and formats: RFC-822, MIME, and their relationship.


Ned Freed
Keith Moore
Dr. John C. Klensin
Jeroen Houttuin

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)