RFC 2852: Deliver By SMTP Service Extension
In plain English — editorial summary, not part of the RFC
This memo defines a mechanism whereby a SMTP client can request, when transmitting a message to a SMTP server, that the server deliver the message within a prescribed period of time. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2852
- Published
- June 2000
- Authors
- D. Newman
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 13
- Also known as
- —
- Updates:
- RFC 1894
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2971IMAP4 ID extensionCurrent
October 2000
- RFC 3028Sieve: A Mail Filtering LanguageObsoleted
January 2001
- RFC 3030SMTP Service Extensions for Transmission of Large and Binary MIME MessagesCurrent
December 2000
- RFC 3207SMTP Service Extension for Secure SMTP over Transport Layer SecurityUpdated
February 2002
- RFC 2476Message SubmissionObsoleted
December 1998
- RFC 2349TFTP Timeout Interval and Transfer Size OptionsCurrent
May 1998
- RFC 2348TFTP Blocksize OptionCurrent
May 1998
- RFC 2347TFTP Option ExtensionCurrent
May 1998
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?