RFC 3461: Simple Mail Transfer Protocol (SMTP) Service Extension for Delivery Status Notifications (DSNs)
In plain English — editorial summary, not part of the RFC
This memo defines an extension to the Simple Mail Transfer Protocol (SMTP) service, which allows an SMTP client to specify (a) that Delivery Status Notifications (DSNs) should be generated under certain conditions, (b) whether such notifications should return the contents of the message, and (c) additional information, to be returned with a DSN, that allows the sender to identify both the recipient(s) for which the DSN was issued, and the transaction in which the original message was sent. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3461
- Published
- January 2003
- Authors
- K. Moore
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 38
- Also known as
- —
- Obsoletes:
- RFC 1891
Topics
Referenced by
5 later RFCs formally update or obsolete part of this document.
- RFC 3798Message Disposition NotificationObsoleted
May 2004
- RFC 3885SMTP Service Extension for Message TrackingCurrent
September 2004
- RFC 5337Internationalized Delivery Status and Disposition NotificationsObsoleted
September 2008
- RFC 6533Internationalized Delivery Status and Disposition NotificationsCurrent
February 2012
- RFC 8098Message Disposition NotificationCurrent
February 2017
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3463Enhanced Mail System Status CodesUpdated
January 2003
- RFC 3464An Extensible Message Format for Delivery Status NotificationsUpdated
January 2003
- RFC 3848ESMTP and LMTP Transmission Types RegistrationCurrent
July 2004
- RFC 3865A No Soliciting Simple Mail Transfer Protocol (SMTP) Service ExtensionCurrent
September 2004
- RFC 3886An Extensible Message Format for Message Tracking ResponsesCurrent
September 2004
- RFC 2821Simple Mail Transfer ProtocolObsoleted
April 2001
- RFC 4130MIME-Based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2 (AS2)Current
July 2005
- RFC 4141SMTP and MIME Extensions for Content ConversionCurrent
November 2005
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?