Transactional email 2 min read

KumoMTA vs Haraka: open-source MTAs for outbound email

A purpose-built high-volume sending MTA or a plugin-driven Node.js SMTP server with outbound delivery. Audience, scope and support compared.

Product data changed. The editorial conclusion needs review. Verified catalogue facts changed; review dependent conclusions.

Two kinds of mail server

KumoMTA is an open-source message transfer agent designed for high-performance outbound email, and its README compares it with commercial enterprise MTAs such as Momentum, PowerMTA and Halon. Haraka is a Node.js SMTP server with a modular plugin architecture, deployed as a filtering MTA or as a submission agent with the auth and DKIM plugins, and it has an outbound delivery engine built in for mail flagged as relaying.

KumoMTA is built around sending; Haraka is a general SMTP server that can also send. Neither README describes an HTTP sending API, a dashboard or templates, so an application team would put its own layer in front of either.

Who is expected to run it

KumoMTA's README states its audience: experienced email operations professionals used to high-performance sending environments and familiar with DevOps practices. Haraka's README is written for people who configure plugins and edit config files, and it shows a plugin hook in a few lines of JavaScript, so it suits teams comfortable writing some Node.js.

Haraka is explicit that it is not a mail store, a local delivery agent or an IMAP server and is meant to work alongside them. For outbound application email that boundary matters less, but mailboxes and inbound storage would come from other software.

Support and licences

KumoMTA keeps GitHub issues for features and bugs, closes help requests posted there, and offers paid support from the publisher. Haraka lists GitHub issues, a mailing list and a screencast for help, and its README describes no paid support. KumoMTA's licence file is the Apache License; Haraka is released under the MIT License.

What this comparison does not show

Haraka's README says it handles thousands of concurrent connections and delivers thousands of messages per second, while KumoMTA's README gives no throughput figure and its hardware guide says it is capable of processing many millions of messages per hour, advising the largest server you can deploy for that volume. Neither claim was tested here, and no deliverability, configuration or security test was run. Servers, IP addresses, DNS and KumoMTA's paid support are separate costs.

Sources

KumoMTA: kumomta-project · Evidence: documentation · Not checked

Haraka: haraka-project · Evidence: documentation · Not checked

Next step

Tools in this guide

All transactional email tools
All guides