Within the Internetemail system, amessage transfer agent (MTA),[1]mail transfer agent,[2] ormail relay issoftware that transfers electronic mail messages from one computer to another using theSimple Mail Transfer Protocol.[3] In some contexts, the alternative namesmail server,mail exchanger, orMX host are used to describe an MTA.
Messages exchanged across networks are passed between mail servers, including any attached data files (such as images, multimedia, or documents). These servers often keep mailboxes for email. Access to this email by end users is typically either bywebmail or anemail client.
A message transfer agent receives mail from either another MTA, amail submission agent (MSA), or amail user agent (MUA). The transmission details are specified by theSimple Mail Transfer Protocol (SMTP). When a recipient mailbox of a message is not hosted locally, the message is relayed, that is, forwarded to another MTA. Every time an MTA receives an email message, it adds aReceived trace header field to the top of the header of the message,[4] thereby building a sequential record of MTAs handling the message. The process of choosing a target MTA for the next hop is also described in SMTP, but can usually be overridden by configuring the MTA software with specific routes.
An MTA works in the background, while the user usually interacts directly with a mail user agent. One may distinguish initial submission as first passing through an MSA—port 465 (or, for legacy reasons, optionally port 587) is used for communication between an MUA and an MSA, while port 25 is used for communication between MTAs, or from an MSA to an MTA.[5] this distinction is clarified inRFC 8314.
For recipients hosted locally, the final delivery of email to a recipient mailbox is the task of amessage delivery agent (MDA). For this purpose the MTA transfers the message to the message handling service component of the message delivery agent (MDA). Upon final delivery, theReturn-Path field is added to the envelope to record thereturn path.
A relay or filtering server will typically store email only briefly, but other systems keep fullmailboxes for email - in which case they usually support some means for end users to access their email via a Mail User Agent (MUA), oremail client.
Common protocols for this are:
Submission of new email from a mail client is via SMTP, typically on port 587 or 465, and is now generally restricted to servers the user has an account with-such as theirISP. This is for policy, not technical, reasons so that providers have some means of holding their users accountable for the generation ofspam and other forms of email abuse.[6]
