Release notes ·
SignalMTA 0.1.2-rc4: A Sharper MTA, with Deep Reporting from BigStats.email
An MTA should be exceptional at moving mail: accepting it safely, queueing it durably, shaping it intelligently, and showing operators exactly what is happening right now. With 0.1.2-rc4 we drew a clear line around that job — and handed long-term analytics to a tool built for it.
Release highlights
Configuration-first WebUI
Domains, authentication, routes, IP pools, traffic shaping, warmup, tenants and streams, submission policy, scripting, nodes, security, and users — all in one focused console.
Live SMTP Log
Watch connections, delivery attempts, and remote replies as mail is processed. This is now the console's operational visibility surface.
CLI metrics
New ./bin/signalmta metrics and --json output give operators and automation direct access to current runtime metrics.
Signed webhooks
HTTP POST delivery events remain a first-class export path — to BigStats.email or to your own HTTPS endpoint.
Compatibility kept
The legacy reports API stays available during the transition, so existing integrations keep working while you move to webhooks.
./bin/signalmta metrics
./bin/signalmta metrics --jsonWhy we moved reporting out of the delivery engine
Every chart rendered inside an MTA console competes with the work the MTA exists to do. Long-window queries, trend storage, and analytics features grow without limit, and they pull engineering attention away from queueing, policy, and delivery. Separating the two keeps SignalMTA lean and predictable under load, while letting reporting evolve as fast as the people reading it need.
What BigStats.email adds
BigStats.email is the recommended reporting layer for SignalMTA. Connect it with a signed webhook and every delivery event flows into a reporting experience designed for deliverability teams and executives alike.
- Historical dashboards. See delivery performance across days, weeks, and months instead of a rolling window inside the MTA.
- Bounce and deferral analysis. Break down failures and temporary rejections by category, provider, and stream to find what is actually hurting delivery.
- Source-IP performance. Compare how each IP and pool performs at each provider — essential for warmup and reputation decisions.
- Provider and domain reporting. Understand how Gmail, Microsoft, Yahoo, and regional providers treat your traffic over time.
- Independent evolution. Reporting improves on its own release cycle without adding load or risk to the delivery engine.
Your telemetry stays yours
BigStats is recommended, never required. SignalMTA remains fully observable on its own: current metrics come from the CLI and runtime APIs, and signed webhooks can feed your own HTTPS analytics endpoint, data warehouse, or SIEM. You choose where delivery data lives.
| SignalMTA license includes | BigStats.email subscription adds |
|---|---|
| MTA runtime, configuration WebUI, Live SMTP Log, CLI/API metrics, signed webhook export | Comprehensive historical reporting and analytics (purchased separately) |
Try 0.1.2-rc4
Start a 30-day Zeta evaluation — no credit card — and follow the updated Evaluation Guide to validate configuration, the Live SMTP Log, CLI metrics, and webhook export in your own environment.