Message Submission for Mail
RFC 6409
also known as STD 72
Revision differences
Document history
Date | By | Action |
---|---|---|
2023-12-12
|
(System) | Imported membership of rfc6409 in std72 via sync to the rfc-index |
2023-12-12
|
(System) | No history of STD72 is currently available in the datatracker before this point |
2020-01-21
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'This memo splits message submission from message relay, allowing each service to operate according to its … Received changes through RFC Editor sync (changed abstract to '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]') |
2015-10-14
|
(System) | Notify list changed from yam-chairs@ietf.org, draft-ietf-yam-rfc4409bis@ietf.org to (None) |
2011-11-16
|
Amy Vezza | Setting stream while adding document to the tracker |
2011-11-16
|
Amy Vezza | Stream changed to IETF from IETF |
2011-11-16
|
Amy Vezza | [Note]: changed to 'Standard 0072' |
2011-11-16
|
Amy Vezza | State changed to RFC Published from RFC Ed Queue. |
2011-11-16
|
(System) | RFC published |