A new Request for Comments is now available in online RFC libraries.
RFC 4409
Title: Message Submission for Mail
Author: R. Gellens, J. Klensin
Status: Standards Track
Date: April 2006
Mailbox: g+ietf@qualcomm.com,
john+ietf@jck.com
Pages: 17
Characters: 34911
Obsoletes: RFC2476
See-Also:
I-D Tag: draft-gellens-submit-bis-02.txt
URL: http://www.rfc-editor.org/rfc/rfc4409.txt
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]
This is now a Draft Standard Protocol.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and
suggestions for improvements.Please refer to the current edition of the
Internet Official Protocol Standards (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
_______________________________________________
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce
