What is an MDA (Mail Delivery Agent)?

Still have a question, spotted an error, or have a better explanation or a source we should cite?

You press send. The email leaves your server (that's the MTA's job). It crosses the internet, lands on the recipient's mail server, and then... what? Something has to put it in their inbox. That's the Mail Delivery Agent (MDA).

The MDA is the final step in the delivery chain. Its job is simple: take the message from the mail server and place it into the user's mailbox. In most systems, the MDA is software like Dovecot, Cyrus, or Maildrop. For webmail services like Gmail or Outlook, the MDA is part of their larger infrastructure. You'll never see it named, but it's there.

Here's the full chain: your ESP hands the email to an MTA (Mail Transfer Agent), which routes it across the internet using SMTP. When it reaches the recipient's mail server, another MTA accepts it. Then the MDA takes over and delivers it to the mailbox, whether that's an IMAP folder, a local maildir, or a database entry in a webmail system.

If you're sending email through an ESP, you don't configure the MDA. That's the recipient's mail server's job. But understanding the MTA-to-MDA handoff helps you debug delivery problems. If your email reaches the recipient's mail server but doesn't appear in their inbox, the issue is often with the MDA's spam filtering rules or mailbox quotas, not with your sending infrastructure.

The sailing metaphor works here: the MTA is the ship that carries cargo across the ocean. The MDA is the dockworker who unloads it and places it in the recipient's warehouse. But unlike a ship, you can't choose which dockworker handles your cargo. That's the recipient's mail server's call.

For most senders, the MDA is invisible. You care about the MTA (your side) and the recipient's spam filter (their side). The MDA sits between them, doing its job quietly. If you're troubleshooting a delivery issue and the logs show the email reached the recipient's server but didn't land in the inbox, that's when understanding the MDA matters. It's not your infrastructure, but it's part of the path your email travels.

Contributors

Who worked on this answer

Every name links to their profile. Every company links to their site. Real people, real accountability.

Ask an AI · tailored to your setup

Ask AI: How does the MDA affect my delivery?

I read this on the Email Almanac about "What is an MDA (Mail Delivery Agent)": "An MDA (Mail Delivery Agent) is the final step in the email delivery chain. After your email crosses the internet via an MTA and reaches the recipient's mail server, the MDA places it into the user's mailbox. For most senders, the MDA is invisible infrastructure on the recipient's side." Help me understand how this applies to MY specific situation. I need: 1. Diagnosis: Based on my setup details below, explain which parts of the MTA/MDA chain I control vs. which parts are handled by the recipient's infrastructure 2. Troubleshooting guide: If emails reach the recipient's server but don't appear in their inbox, what should I check first? Provide a ranked checklist 3. Common misconceptions: What do senders often misunderstand about the MDA's role, and how does that lead to wasted troubleshooting time? 4. When to escalate: At what point should I stop blaming the MDA and look at spam filtering, authentication, or sender reputation instead? --- My details (the more you share, the better the advice): - Email platform/ESP: e.g. Mailchimp, SendGrid, custom SMTP, self-hosted - Domain(s): your sending domain - Sending volume: e.g. 1,000/month, 10,000/day - Experience level: beginner / intermediate / advanced - What I'm building: newsletter, transactional emails, marketing campaigns - Current challenge: describe what prompted this question

Edit the yellow boxes, then send to the AI of your choice.