Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Local Mail Transfer Protocol
open-in-new
<h2 id="overview">Overview</h2> <p>Mail queues are an inherent requisite of SMTP. In situations in which mail queues are not possible, LMTP is desirable, since a mail storage server should manage only its mail store without having to allocate more storage for a mail queue. This is not possible with SMTP when there are multiple recipients for a mail message. SMTP can only indicate successful delivery or failure for all or none of the recipients, creating the need for a separate queue to handle the failed recipients. </p><p>LMTP, on the other hand, can indicate success or failure to the client for each recipient, allowing the client to handle the queueing instead. The client in this case would typically be an Internet-facing mail gateway. LMTP is not intended for use over <a href="/facts/Wide_area_network/mAkW4gr3">wide area networks</a>. In other words, the <a href="/facts/Message_transfer_agent/9SJG5sbb">message transfer agent</a> (MTA) still handles all outgoing mail, including the mail stream from the LMTP, to another mail server located somewhere on the Internet. </p><p>LMTP is an <a href="/facts/Application_Layer/FAFhLruA">Application Layer</a> protocol of the <a href="/facts/Internet_Protocol_Suite/KNkxtSpw">Internet Protocol Suite</a>. It can use a <a href="/facts/Transmission_Control_Protocol/WW4sPrt9">Transmission Control Protocol</a> (TCP) transport like SMTP, but must not use <a href="/facts/Port_number/ygoHVKNC">port number</a> 25, the <a href="/facts/Well-known_port/c30Xg4d4">well-known port</a> for SMTP. Usage of port 24 ("any private mail system") is common among some mail server applications however.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> </p> <h2 id="differences-from-smtp">Differences from SMTP</h2> <p>LMTP conversation syntax is based on the same commands as SMTP (formerly called Extended SMTP) with the following exceptions:<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> </p> <ul><li>LMTP must not be used on port 25, reserved for SMTP</li> <li>LMTP uses LHLO verb instead of EHLO or HELO used in SMTP</li> <li>ESMTP requires a single status for the entire message body. LMTP requires a response for each previously successful RCPT command. That is, in case of multiple recipients, after the body of the message has been transmitted, LMTP can still fail for some recipient while succeeding for the others. With this facility, LMTP can fail if a user is over quota without the burden of generating <a href="/facts/Bounce_message/vDJLbP2p">bounce messages</a>.</li></ul> <p>The key difference is that LMTP will reject a message for a specific final recipient if it is not immediately deliverable. This removes the need for a mail queue. For this reason, LMTP is not run on the standard TCP port of SMTP. </p> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>Myers, J. "Local Mail Transfer Protocol". tools.ietf.org. Retrieved 2021-03-03. <a href="https://tools.ietf.org/html/rfc2033.html" target="_blank">https://tools.ietf.org/html/rfc2033.html</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>Venema, Wietse. "Postfix manual - smtp(8)". LMTP DESTINATION SYNTAX. p. 2. Retrieved 16 September 2017. <a href="http://www.postfix.org/lmtp.8.html" target="_blank">http://www.postfix.org/lmtp.8.html</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>Myers, J. "Local Mail Transfer Protocol". tools.ietf.org. Retrieved 2021-03-03. <a href="https://tools.ietf.org/html/rfc2033.html" target="_blank">https://tools.ietf.org/html/rfc2033.html</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> </ol>