{"draft":"draft-ietf-yam-rfc4409bis-03","doc_id":"RFC6409","title":"Message Submission for Mail","authors":["R. Gellens","J. Klensin"],"format":["ASCII","HTML"],"page_count":"20","pub_status":"INTERNET STANDARD","status":"INTERNET STANDARD","source":"Yet Another Mail","abstract":"This memo splits message submission from message relay, allowing each\r\nservice to operate according to its own rules (for security, policy,\r\netc.), and specifies what actions are to be taken by a submission\r\nserver.\r\n\r\nMessage relay is unaffected, and continues 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.  \r\n[STANDARDS-TRACK]","pub_date":"November 2011","keywords":["[--------]","Text","Internationalization","ASCII","Unicode","UTF-8"],"obsoletes":["RFC4409"],"obsoleted_by":[],"updates":[],"updated_by":["RFC8314"],"see_also":["STD0072"],"doi":"10.17487\/RFC6409","errata_url":"https:\/\/www.rfc-editor.org\/errata\/rfc6409"}