RFC 4405: SMTP Service Extension for Indicating the Responsible Submitter of an E-Mail Message
In plain English — editorial summary, not part of the RFC
This memo defines an extension to the Simple Mail Transfer Protocol (SMTP) service that allows an SMTP client to specify the responsible submitter of an e-mail message. The responsible submitter is the e-mail address of the entity most recently responsible for introducing a message into the transport stream. This extension helps receiving e-mail servers efficiently determine whether the SMTP client is authorized to transmit mail on behalf of the responsible submitter's domain. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC4405
- Published
- April 2006
- Authors
- E. Allman; H. Katz
- Status
- HISTORIC
- Stream
- IETF
- Area
- —
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4871DomainKeys Identified Mail (DKIM) SignaturesObsoleted
May 2007
- RFC 4406Sender ID: Authenticating E-MailCurrent
April 2006
- RFC 5068Email Submission Operations: Access and Accountability RequirementsUpdated
November 2007
- RFC 6651Extensions to DomainKeys Identified Mail (DKIM) for Failure ReportingCurrent
June 2012
- RFC 6652Sender Policy Framework (SPF) Authentication Failure Reporting Using the Abuse Reporting FormatCurrent
June 2012
- RFC 4408Sender Policy Framework (SPF) for Authorizing Use of Domains in E-Mail, Version 1Obsoleted
April 2006
- RFC 5429Sieve Email Filtering: Reject and Extended Reject ExtensionsCurrent
March 2009
- RFC 5452Measures for Making DNS More Resilient against Forged AnswersCurrent
January 2009
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?