MTA (Mail Transfer Agent)
The MTA is the software that moves email between servers: queueing, retrying, and speaking SMTP. What it does, common implementations, and where it sits in the stack.
An MTA (Mail Transfer Agent) is the software that transfers email between servers: it accepts messages, queues them, resolves where they should go, speaks SMTP to the destination, and retries with backoff when delivery fails. Every message you have ever sent passed through at least two MTAs, the sender's and the receiver's, and often several more. When deliverability engineers talk about queues, retries, deferral handling, or connection throttling, they are talking about MTA behaviour.
What an MTA actually does
The core loop: accept a message (from an application, a user's mail client via submission, or another server), write it durably to a queue, look up the destination's MX records, connect and attempt delivery, and interpret the response. Success dequeues the message; a permanent failure generates a bounce back to the envelope sender; a temporary failure schedules a retry on a backoff curve, typically over several days before giving up. That queue-and-retry discipline is what makes email resilient: receivers can be down for hours and lose nothing.
Around the core, production MTAs carry the policy load: DKIM signing via filters, rate limiting per destination so receivers are not slammed, TLS negotiation including MTA-STS and DANE awareness, bounce generation, and on the inbound side the gatekeeping (greylisting, sender checks, spam filter handoff) that receivers run before accepting responsibility for a message.
The cast around it
The MUA (Mail User Agent) is the client humans use: Gmail's interface, Outlook, Apple Mail. The MDA (Mail Delivery Agent) writes accepted mail into mailboxes. A smarthost is an MTA that other machines relay through, the classic pattern for giving legacy systems one stable outbound door. An ESP is a business wrapping fleets of MTAs plus data processing into a service. Common self-hosted implementations: Postfix (the default choice), Exim, and OpenSMTPD, with commercial MTAs (PowerMTA, Halon, KumoMTA) powering high-volume senders and ESPs.
Frequently asked questions
Is an MTA the same as a mail server?
How long do MTAs retry before bouncing?
Do I need my own MTA if I use an ESP?
Key takeaways
- The MTA transfers mail between servers: accept, queue, resolve MX, deliver, retry with backoff
- Queue-and-retry discipline is what makes email survive outages measured in days
- Production MTAs also carry policy: signing, rate limiting, TLS enforcement, and inbound gatekeeping
- MUA, MDA, smarthost, and ESP name the neighbours; Postfix and Exim are the standard self-hosted implementations