idnits 2.17.1 draft-ietf-drums-smtpupd-13.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 2821 5 Title: Simple Mail Transfer Protocol 6 Author(s): J. Klensin, Editor 7 Status: Standards Track 8 Date: April 2001 9 Mailbox: klensin@research.att.com 10 Pages: 79 11 Characters: 192504 12 Updates: 1123 13 Obsoletes: 821, 974 15 I-D Tag: draft-ietf-drums-smtpupd-13.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc2821.txt 19 This document is a self-contained specification of the basic protocol 20 for the Internet electronic mail transport. It consolidates, updates 21 and clarifies, but doesn't add new or change existing functionality of 22 the following: 24 - the original SMTP (Simple Mail Transfer Protocol) specification of 25 RFC 821, 27 - domain name system requirements and implications for mail 28 transport from RFC 1035 and RFC 974, 30 - the clarifications and applicability statements in RFC 1123, 31 and 33 - material drawn from the SMTP Extension mechanisms. 35 It obsoletes RFC 821, RFC 974, and updates RFC 1123 (replaces the 36 mail transport materials of RFC 1123). However, RFC 821 specifies 37 some features that were not in significant use in the Internet by the 38 mid-1990s and (in appendices) some additional transport models. Those 39 sections are omitted here in the interest of clarity and brevity; 40 readers needing them should refer to RFC 821. 42 It also includes some additional material from RFC 1123 that required 43 amplification. This material has been identified in multiple ways, 44 mostly by tracking flaming on various lists and newsgroups and 45 problems of unusual readings or interpretations that have 46 appeared as the SMTP extensions have been deployed. Where this 47 specification moves beyond consolidation and actually differs from 48 earlier documents, it supersedes them technically as well as 49 textually. 51 Although SMTP was designed as a mail transport and delivery protocol, 52 this specification also contains information that is important to its 53 use as a 'mail submission' protocol, as recommended for POP and IMAP. 55 Additional submission issues are discussed in RFC 2476. 57 Section 2.3 provides definitions of terms specific to this document. 58 Except when the historical terminology is necessary for clarity, this 59 document uses the current 'client' and 'server' terminology to 60 identify the sending and receiving SMTP processes, respectively. 62 A companion document discusses message headers, message bodies 63 and formats and structures for them, and their relationship. 65 This document is a product of the Detailed Revision/Update of Message 66 Standards Working Group of the IETF. 68 This is now a Proposed Standard Protocol. 70 This document specifies an Internet standards track protocol for 71 the Internet community, and requests discussion and suggestions 72 for improvements. Please refer to the current edition of the 73 "Internet Official Protocol Standards" (STD 1) for the 74 standardization state and status of this protocol. Distribution 75 of this memo is unlimited. 77 This announcement is sent to the IETF list and the RFC-DIST list. 78 Requests to be added to or deleted from the IETF distribution list 79 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 80 added to or deleted from the RFC-DIST distribution list should 81 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 83 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 84 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 85 help: ways_to_get_rfcs. For example: 87 To: rfc-info@RFC-EDITOR.ORG 88 Subject: getting rfcs 90 help: ways_to_get_rfcs 92 Requests for special distribution should be addressed to either the 93 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 94 specifically noted otherwise on the RFC itself, all RFCs are for 95 unlimited distribution.echo 96 Submissions for Requests for Comments should be sent to 97 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 98 Authors, for further information.