Search RFCs

RFC Editor

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 listyam@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 eachservice to operate according to its own rules (for security, policy,etc.), and specifies what actions are to be taken by a submissionserver.

Message relay is unaffected, and continues to use SMTP over port 25.

When conforming to this document, message submission uses theprotocol specified here, normally over port 587.

This separation of function offers a number of benefits, includingthe ability to apply specific security or policy requirements. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.