Message submission agent

<h2 id="benefits">Benefits</h2>
<p>Separation of the <a href="/facts/Mail_transfer_agent/9SJG5sbb">MTA</a> and MSA functions produces several benefits.
</p><p>One benefit is that an MSA, since it is interacting directly with the author's MUA, can correct minor errors in a message format (such as a missing <i>Date</i>, <i><a href="/facts/Message-ID/MzMWt17h">Message-ID</a></i>, <i>To</i> fields, or an address with a missing domain name) and/or immediately report an error to the author so that it can be corrected before it is sent to any of the recipients. An MTA accepting a message from another site cannot reliably make those kinds of corrections, and any error reports generated by such an MTA will reach the author (if at all) only after the message has already been sent.
</p><p>One more benefit is that with a dedicated port number, 587, it is always possible for users to connect to <i>their domain</i> to submit new mail. To combat spam (including spam being sent unwittingly by a victim of a <a href="/facts/Botnet/bGspY7bJ">botnet</a>) many <a href="/facts/Internet_service_provider/dUacAxef">ISPs</a> and institutional <a href="/facts/Computer_network/3w5RM99p">networks</a> restrict the ability to connect to remote MTAs on port 25. The accessibility of an MSA on port 587<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> enables nomadic users (for example, those working on a laptop) to continue to send mail via their preferred submission servers even from within others' networks. Using a specific submission server is a requirement when <a href="/facts/Sender_Policy_Framework/H7qCzXE2">sender policies</a> or <a href="/facts/Author_Domain_Signing_Practices/2MYycmNt">signing practices</a> are enforced.
</p><p>Another benefit is that separating the MTA and MSA functions makes it easier for an MTA to deny relaying, that is to refuse any mail that is not addressed to a recipient at a domain that is served locally. This is a strategy used by ISPs to prevent the sending of spam from virus-infected client computers. By contrast, an MSA must generally accept mail for any recipient on the Internet, though it only accepts such mail from authors who are authorized to use that MSA and who have established their identity to the MSA via authentication. In times when both mail submission and acceptance of incoming mail were usually accomplished using the same protocol and the same server, the ability to send mail to arbitrary destinations without authentication allowed spammers to use MTAs as a means of distributing <a href="/facts/E-mail_spam/ARJr6Aem">spam</a> (since a single message transaction can request that an MTA relay a message to a large number of recipients), and also made it more difficult to trace a message to its origin.
</p><p>Moreover, MSAs and MTAs can have different policies for filtering of spam. Most MSAs require authentication in the form of a username and password provided by the author. Any messages received by such an MSA are therefore traceable to an author who has a direct relationship with the MSA, and who can be held accountable for his actions. This allows the MSA to have either no spam filtering, or more permissive spam filtering than an MTA that exists for the purpose of accepting incoming email from other domains. It is difficult to establish trust in mail sent between arbitrary domains, because there is generally no direct relationship between those domains via which trust, or even identity, can be established. In the absence of such trust, an MTA must generally rely on heuristics and third-party reputation services to distinguish spam from legitimate traffic, and both of these mechanisms have a history of being error-prone.<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a><a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a> The separation of MSA and MTA therefore avoids the use of unreliable spam recognition mechanisms during mail submission, and increases the probability for legitimate mail to be delivered successfully.
</p>
<h2 id="protocol">Protocol</h2>
<h3>Configuration</h3>
<p>While recent <a href="/facts/Email_client/pQdW9HtC">email clients</a> use port 587 by default, older ones still propose port 25.  Users have to change the port number manually in the latter case.  It is also possible that the MUA may automatically discover which server provides the MSA for a given domain, looking up the <a href="/facts/SRV_record/5JdIlqDm">SRV records</a> for that domain.  Domain example.com can publish its record like so:<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a>
</p>
  _submission._tcp.example.com.     SRV 0 1 587 mail.example.com.

<h3>Mandatory authentication</h3>
<p class="note">Main article: <a href="/facts/SMTP_Authentication/YcQqoSqf">SMTP Authentication</a></p>
<p>RFC 6409 requires that clients are authorized and authenticated to use the mail submission service, e.g., as described in SMTP-AUTH (ESMTPA), or by other means such as <a href="/facts/RADIUS/9Gr9deYD">RADIUS</a>, <a href="/facts/Public_key_certificate/J7aYI4Bx">public key certificates</a>, or (the mostly obsolete) <a href="/facts/POP_before_SMTP/GwSuHS2G">POP before SMTP</a>.
</p>
<h3>Policy enforcement</h3>
<p>The MSA must check that the submitted mail is syntactically valid and conforms to the relevant site policies. RFC 6409 contains some optional features:
</p>
<ul><li><i>Enforce submission rights</i> guarantees that the <a href="/facts/Bounce_address/mngvEe6V">envelope sender address</a> is valid and authorized with the used authentication. This in essence complies with the <a href="/facts/Sender_policy_framework/H7qCzXE2">SPF</a> model specified in RFC 7208.</li>
<li><i>May add sender</i> permits to add a Sender address header field if the <a href="/facts/Bounce_address/mngvEe6V">envelope sender address</a> does not match any author address in the "From" header field. This roughly complies with the <a href="/facts/Sender_ID/9l3kJ2oT">Sender ID</a> model specified in RFC 4406 – ignoring the tricky case of Resent-From header fields not covered in RFC 6409.</li></ul>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/E-mail_authentication/NWelESMa">E-mail authentication</a></li>
<li><a href="/facts/List_of_mail_servers/UCbnt4ke">List of mail servers</a></li>
<li><a href="/facts/Comparison_of_mail_servers/59YCMzxV">Comparison of mail servers</a></li>
<li><a href="/facts/Smart_host/WCt8o0jh">Smart host</a></li>
<li><a href="/facts/E-mail_agent_(infrastructure)/9A8CLSs3">E-mail agent (infrastructure)</a> (MxA)</li>
<li><a href="/facts/Mail_delivery_agent/Syntl05o">Mail delivery agent</a> (MDA)</li>
<li><a href="/facts/Mail_user_agent/pQdW9HtC">Mail user agent</a> (MUA)</li></ul>

<ul><li>Klensin, J. (April 2001). <a href="https://datatracker.ietf.org/doc/html/rfc2821"><i>Simple Mail Transfer Protocol</i></a>. <a href="/facts/Internet_Engineering_Task_Force/tIcCsFhX">IETF</a>. <a href="/facts/Doi_(identifier)/muM9Etpq">doi</a>:<a href="https://doi.org/10.17487%2FRFC2821">10.17487/RFC2821</a>. <a href="/facts/Request_for_Comments/esftTvE7">RFC</a> <a href="https://datatracker.ietf.org/doc/html/rfc2821">2821</a>. Retrieved November 14, 2013.</li>
<li><a href="http://kasoft.freeyellow.com/Central/smtpbad.html">"SMTP is not secure"</a>. <i>Kasoft Central</i>. Retrieved 2008-06-14.</li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>Gellens, R.; Klensin, J. (November 2011). "Submission Identification". Message Submission for Mail. IETF. sec. 3.1. doi:10.17487/RFC6409. STD 72. RFC 6409. Retrieved November 14, 2013. <a href="https://datatracker.ietf.org/doc/html/rfc6409#section-3.1" target="_blank">https://datatracker.ietf.org/doc/html/rfc6409#section-3.1</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
<li id="fn:2"><p>Costales, Bryan; Assmann, Claus; Jansen, George; Shapiro, Gregory Neil (2007-10-26). sendmail: Build and Administer sendmail. "O'Reilly Media, Inc.". ISBN 978-0-596-55534-4. <a href="978-0-596-55534-4" target="_blank">978-0-596-55534-4</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li>
<li id="fn:3"><p>Gellens, R.; Klensin, J. (November 2011). "Submission Identification". Message Submission for Mail. IETF. sec. 3.1. doi:10.17487/RFC6409. STD 72. RFC 6409. Retrieved November 14, 2013. <a href="https://datatracker.ietf.org/doc/html/rfc6409#section-3.1" target="_blank">https://datatracker.ietf.org/doc/html/rfc6409#section-3.1</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li>
<li id="fn:4"><p>C. Hutzler; D. Crocker; P. Resnick; E. Allman; T. Finch (November 2007). Email Submission Operations: Access and Accountability Requirements. IETF. doi:10.17487/RFC5068. RFC 5068. Retrieved 13 February 2013. Access Providers MUST NOT block users from accessing the external Internet using the SUBMISSION port 587. <a href="/wiki/Eric_Allman" target="_blank">/wiki/Eric_Allman</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li>
<li id="fn:5"><p>Amir Herzberg (19 May 2009). "DNS-based email sender authentication mechanisms: A critical review". Computers & Security. 28 (8): 731–742. doi:10.1016/j.cose.2009.05.002. <a href="/wiki/Doi_(identifier)" target="_blank">/wiki/Doi_(identifier)</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li>
<li id="fn:6"><p>Jeremy Blosser and David Josephsen (November 2004). "Scalable Centralized Bayesian Spam Mitigation with Bogofilter". Proceedings of LISA '04: Eighteenth Systems Administration Conference. USENIX. Retrieved 24 June 2010. <a href="http://www.usenix.org/event/lisa04/tech/blosser/blosser_html/" target="_blank">http://www.usenix.org/event/lisa04/tech/blosser/blosser_html/</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li>
<li id="fn:7"><p>Cyrus Daboo (March 2011). "Email Submission". Use of SRV Records for Locating Email Submission/Access Services. IETF. sec. 3.1. doi:10.17487/RFC6186. RFC 6186. Retrieved 17 April 2013. <a href="https://datatracker.ietf.org/doc/html/rfc6186#section-3.1" target="_blank">https://datatracker.ietf.org/doc/html/rfc6186#section-3.1</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li>
</ol>

Message submission agent open-in-new

Message submission agent