database logo graphic

RFC 4409

"Message Submission for Mail", April 2006

Canonical URL:
http://www.rfc-editor.org/rfc/rfc4409.txt
This document is also available in this non-normative format: PDF.
Status:
DRAFT STANDARD
Obsoletes:
RFC 2476
Obsoleted by:
RFC 6409
Authors:
R. Gellens
J. Klensin
Stream:
IETF
Source:
NON WORKING GROUP

Cite this RFC: TXT  |  XML

Other actions: Find Errata (if any)  |  Submit Errata  |  Find IPR Disclosures from the IETF


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 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]


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Go to the RFC Editor Homepage.