Message Submission for Mail
RFC 4409
Revision differences
Document history
Date | By | Action |
---|---|---|
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 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]') |
2015-10-14
|
(System) | Notify list changed from john+ietf@jck.com, randy@qualcomm.com to (None) |
2006-04-25
|
Amy Vezza | State Changes to RFC Published from RFC Ed Queue by Amy Vezza |
2006-04-25
|
Amy Vezza | [Note]: 'RFC 4409' added by Amy Vezza |
2006-04-24
|
(System) | RFC published |