metasystema.org
UpdatedINTERNET STANDARDIETF streamSTD72

RFC 6409: Message Submission for Mail

Still current, but amended. Parts of this document are changed or extended by RFC 8314. Read both.

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

Document record

Document ID
RFC6409
Published
November 2011
Authors
R. Gellens; J. Klensin
Status
INTERNET STANDARD
Stream
IETF
Area
app
Pages
20
Also known as
STD72
Obsoletes:
RFC 4409
Updated by:
RFC 8314

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 2476 (1998)
  2. RFC 4409 (2006)
  3. RFC 6409 (2011)

Read the full history of Message Submission for Mail →

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.

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?

canonical URL: /rfc/6409-message-submission-for-mail