- File formats:
- Status:
- INTERNET STANDARD
- Obsoletes:
- RFC 4409
- Updated by:
- RFC 8314
- Authors:
- R. Gellens
J. Klensin - Stream:
- IETF
- Source:
- yam (app)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC6409
Discuss this RFC: Send questions or comments to the mailing list yam@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 6409
Abstract
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 is unaffected, and continues 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]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.