What is an MTA vendor (GreenArrow, PowerMTA, Halon, etc.)?
Still have a question, spotted an error, or have a better explanation or a source we should cite?
Most senders never need to think about MTA vendors. You sign up for Amazon SES or Mailgun, point your DNS, and start sending. Job done. But there's a whole category of infrastructure that sits underneath those services, and if you're building an ESP, running a high-volume internal email operation, or need control that no shared platform will give you, that's where MTA vendors come in.
An MTA (Mail Transfer Agent) is the software that actually moves email between servers. Commercial MTA vendors sell you that software (or host it for you) with enterprise-grade features built on top of it.
The main players are GreenArrow, PowerMTA (now Bird), Halon, and Momentum. What they all share is a feature set that generic SMTP providers don't expose to you directly: granular throttling per receiving domain, per-IP and per-campaign queue management, deep bounce classification, traffic shaping rules, and detailed delivery analytics at the message level.
If you're sending tens of millions of emails a day, that granularity matters a lot. You can tell your MTA to slow down for one ISP while pushing full speed to another. You can route VIP transactional traffic over dedicated IPs while your marketing campaigns go over a separate pool. You can react to a remote server's feedback in real time rather than waiting for a support ticket to get resolved.
There's also an open-source contender worth knowing. KumoMTA was built as a modern open-source alternative that matches commercial MTA capabilities (adaptive delivery, traffic shaping, bounce classification) without licensing fees. Its business model runs on support and consulting instead. It competes directly with the paid vendors on raw features, which is something that wasn't really true of older open-source options.
So who actually uses these? Primarily three groups: ESPs building their own sending platforms, large enterprises running internal email infrastructure at scale, and high-volume senders (think major retailers, banks, or ISPs) who need full ownership of the stack. If you're not in one of those groups, you almost certainly don't need one. (And if you're not sure which group you're in, that's a pretty clear signal you don't need one yet.)
If you're at the stage of evaluating infrastructure options, it's honestly worth a conversation with someone who's done it. Our SOS hotline is free and we won't try to sell you something you don't need.
Contributors
Who worked on this answer
Every name links to their profile. Every company links to their site. Real people, real accountability.
