RFC 4409: Message Submission for Mail
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6409.
Current document in this lineage: RFC 6409 — Message Submission for Mail
In plain English — editorial summary, not part of the RFC
This memo splits message submission from message relay, allowing each service to operate according to its own rules (for security, policy, etc.), and specifies what actions are to be taken by a submission server. Message relay and final delivery are unaffected, and continue to use SMTP over port 25. When conforming to this document, message submission uses the protocol specified here, normally over port 587. This separation of function offers a number of benefits, including the ability to apply specific security or policy requirements. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4409
- Published
- April 2006
- Authors
- R. Gellens; J. Klensin
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 17
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2476 (1998)
- RFC 4409 (2006)
- RFC 6409 (2011) ✓
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4189Requirements for End-to-Middle Security for the Session Initiation Protocol (SIP)Current
October 2005
- RFC 4730A Session Initiation Protocol (SIP) Event Package for Key Press Stimulus (KPML)Current
November 2006
- RFC 3938Video-Message Message-ContextCurrent
October 2004
- RFC 4916Connected Identity in the Session Initiation Protocol (SIP)Current
June 2007
- RFC 3840Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)Current
August 2004
- RFC 3458Message Context for Internet MailUpdated
January 2003
- RFC 3421Select and Sort Extensions for the Service Location Protocol (SLP)Current
November 2002
- RFC 3329Security Mechanism Agreement for the Session Initiation Protocol (SIP)Updated
January 2003
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?