{"draft":"draft-gellens-submit-bis-02","doc_id":"RFC4409","title":"Message Submission for Mail","authors":["R. Gellens","J. Klensin"],"format":["ASCII","HTML"],"page_count":"17","pub_status":"DRAFT STANDARD","status":"DRAFT STANDARD","source":"IETF - NON WORKING GROUP","abstract":"This memo splits message submission from message relay, allowing\r\neach service to operate according to its own rules (for security,\r\npolicy, etc.), and specifies what actions are to be taken by a\r\nsubmission server.\r\n\r\nMessage relay and final delivery are unaffected, and continue to use SMTP over port 25.\r\n\r\nWhen conforming to this document, message submission uses the\r\nprotocol specified here, normally over port 587.\r\n\r\nThis separation of function offers a number of benefits, including\r\nthe ability to apply specific security or policy requirements.  [STANDARDS-TRACK]","pub_date":"April 2006","keywords":["smtp","simle mail transfer protocol","ua","user agent"],"obsoletes":["RFC2476"],"obsoleted_by":["RFC6409"],"updates":[],"updated_by":[],"see_also":[],"doi":"10.17487\/RFC4409","errata_url":"https:\/\/www.rfc-editor.org\/errata\/rfc4409"}