Flagship · one script, a complete ESP server
From bare server to sending —
in under an hour.
The Auto PMTA Configurator is a single deployment script that installs the full stack, generates every domain's authentication, publishes DNS through Cloudflare, brings dual-stack IPv4+IPv6 VMTAs online, and hands you a real-time dashboard — then keeps it healthy with 47 ongoing operations. Bring your own PowerMTA license.
The Auto PMTA Configurator is a deployment and management tool that turns a clean server into a complete, production email-sending platform — typically in under an hour. It works with PowerMTA 6.0r2, any PowerMTA 5.x, and KumoMTA (all versions): bring your own PowerMTA license, or run KumoMTA, which is open-source and free. It installs the full stack, generates and publishes every domain's authentication, brings dual-stack IPv4 and IPv6 sending online, and then runs the platform with 47 day-to-day operations. On KumoMTA it also generates and integrates an administrative panel the project doesn't ship with, so configuration changes and metrics are a few clicks rather than hand-edited Lua. The price is €799 once, with no subscription. What follows is exactly what it does, what it needs from you, and where the €799 sits next to the alternatives.
Auto PMTA Configurator
No subscription · no monthly fees
Get the Configurator →PowerMTA 6.0r2 / 5.x · or free KumoMTA
Infrastructure capacity
- Domains per server
- Up to 256
- IPv4 VMTAs
- Up to 256
- IPv6 VMTAs
- Up to 2,560
- Throughput
- 2M+ emails/day per server
- Multi-client
- Isolated clients per server
- Stack
- PowerMTA 6.0r2 / 5.x or KumoMTA · Postfix · Dovecot · Nginx
The problem it solves
PowerMTA is powerful. Configuring it correctly is the hard part.
PowerMTA is one of the most capable high-volume mail engines a sender can run, and that reputation is earned. The catch is that the capability lives in the configuration, and the configuration is where most people lose days. Standing up a real sending platform is far more than installing a binary: you define virtual MTAs and IP pools, set up DKIM, SPF, DMARC, MTA-STS and reverse DNS for every domain, issue TLS certificates, write firewall rules, wire bounce and feedback-loop processing, build suppression handling, and tune per-provider throttling so a full-list send doesn't trip Gmail or Microsoft.
Every one of those is a place to be subtly wrong, and a subtle mistake in authentication or reverse DNS rarely throws an obvious error — it just quietly costs you the inbox. Operators who run PowerMTA describe its configuration as a genuine learning curve precisely because the engine assumes you already know how high-volume sending is supposed to be wired. That knowledge is exactly what the Configurator encodes: the full sequence an experienced deliverability engineer would run by hand, turned into one deterministic deploy that does it the same way every time.
The result is that the expertise gap stops being your problem on day one. You don't spend a week reading documentation and debugging why Gmail is deferring you; you run the deploy, watch the four phases complete, and start from a server that is already authenticated, already routing correctly, and already visible in a dashboard.
From bare server to sending
Four automated phases
Full stack, from a bare server
Installs and configures everything on a clean AlmaLinux 8/9, Rocky 8/9, Debian 12/13, Fedora or Ubuntu box — your engine (PowerMTA or KumoMTA), Postfix, Dovecot, Nginx, Node.js, Python, CSF firewall and all dependencies.
Domain identities generated
Per domain: DKIM 2048 (with rotation), optimized SPF, DMARC p=reject with RUA/RUF, MTA-STS, TLS-RPT, and IPv6 AAAA/PTR — published directly via the Cloudflare API.
DNS propagation verified
Confirms every record propagated correctly before continuing — DKIM, SPF, DMARC, MTA-STS and IPv4/IPv6 PTRs — with a per-domain status report.
Production config applied
Generates and applies the full PowerMTA, Postfix, Dovecot and Nginx config: dual-stack VMTAs, IP pools, authenticated SMTP listeners, Let's Encrypt SSL, MailWizz integration and per-client dashboards.
The phases run end to end without supervision. The longest wait is usually DNS propagation between Phase 1 and Phase 2 — and even that is handled for you, because Phase 2 won't continue until it has confirmed each record resolves correctly. By the end of Phase 3 the server is accepting mail, signing it, routing it per provider, and reporting on it, with authentication verified rather than left on a checklist.
Because the configuration is deterministic, a deploy is reproducible. The same domains file always produces the same result, so you can rebuild a server identically, stand up a second one to match, or hand the configuration to a colleague and know exactly what it will do. That predictability is the difference between a setup you can audit and a hand-built box only one person understands.
What you'd be watching
The real-time dashboard
Every client gets a live Node.js panel over HTTPS — delivered, deferred and bounced volumes, queue depth, per-provider acceptance and IP health, updating as it sends.
Delivered
0
today
Deferred
0
retrying
Bounced
0
0%
Queue
0
in flight
Acceptance by provider
Day-to-day control
47 management operations
Deployment is half the job. The Configurator gives you everything to run the platform afterwards, grouped into the work you actually do.
Monitoring & diagnostics
- ✓Real-time per-client metrics dashboard (Node.js, HTTPS)
- ✓DNS check across all domains at once
- ✓Blacklist monitoring on every IP
- ✓Full IPv4 & IPv6 diagnostics
- ✓9-module system health check
- ✓Live PowerMTA logs with filters
Deliverability & reputation
- ✓MailReach warming via API (batch, custom sender/port/prefix)
- ✓Seed-list inbox-placement testing
- ✓BIMI brand logo (Gmail, Yahoo, Apple Mail)
- ✓Adaptive per-ISP throttling (auto + manual)
- ✓Progressive IP-warming scheduler
- ✓Postmaster registration (SNDS, Yahoo/AOL FBL, Apple, Barracuda)
IP & network
- ✓Active-vs-required IP verification
- ✓Audit & repair downed IPs without reinstall (persists across reboot)
- ✓Domain migration between IPs with no downtime
- ✓Granular manual per-ISP throttling
ESP integration
- ✓Automatic MailWizz config (delivery + bounce servers)
- ✓CSV export ready for MailWizz import
- ✓SendGrid v3-compatible API gateway
- ✓Delivery-server management: enable, disable, audit
Security & compliance
- ✓CSF firewall, fully configured and managed
- ✓Auto SSL/TLS (Let's Encrypt) with auto-renewal
- ✓Authenticated SMTP, credentials per domain
- ✓Global suppression: hard bounces, FBL, disposable domains
- ✓SMTP credential audit
- ✓Suppression list import/export
Maintenance & alerts
- ✓Automatic & manual config backup
- ✓Controlled maintenance mode (pause without losing queues)
- ✓Auto-repair of known errors
- ✓Queue management: view, pause, resume, flush
- ✓Real-time Telegram alerts (bounces, blacklists, SSL, services)
- ✓Webhook to MailWizz for PowerMTA events
This is the part most setup services and one-click installers leave out. Getting a server sending is the opening move; keeping it sending — catching a blacklisting the hour it happens, pausing a queue without losing it, repairing a downed IP without a rebuild, renewing SSL before it lapses — is the work that protects the reputation you spent weeks building. The Configurator treats that ongoing operation as part of the product, not an afterthought you're left to script yourself. In practice that means a blacklisting surfaces as a Telegram alert while you can still act on it, a queue can be paused for maintenance and resumed later without losing a single message, an expiring certificate renews before it lapses, and an IP that drops out gets repaired and re-added on its own — the small saves that, across a year of sending, separate steady inbox placement from a slow, unexplained decline.
What you bring
Three things, and the Configurator does the rest
There's no long prerequisites list. If you have these three, you can deploy today.
Your engine: PowerMTA or KumoMTA
PowerMTA 6.0r2 or any 5.x (a valid, licensed copy you supply), or KumoMTA (open-source and free, any version). The Configurator installs and configures it; it never bundles, resells or cracks PowerMTA, and it won't run against a nulled build.
A clean server
A bare AlmaLinux 8/9, Rocky Linux 8/9, Debian 12/13, Fedora or Ubuntu box with the sending IPv4 addresses you intend to use, plus an IPv6 block if you have one. No control panel — it runs straight on the OS.
Your domains and DNS
The sending domains you own, and a Cloudflare account so every authentication record can be published through the API and verified before the server goes live.
The licence question is the one people ask first, so to be plain about it: the Configurator does not include PowerMTA and does not get you around needing it. PowerMTA is commercial software you license from its vendor; the Configurator installs and configures the copy you hold. If you don't yet have a licence, our PowerMTA pricing & licence guide walks through how that side works, and the alternatives if you'd rather not run a commercial engine at all.
Where the €799 sits
One-time, not another monthly bill
The Configurator isn't competing with PowerMTA's licence — that's the engine you bring. It's competing with the two slow, expensive ways people usually get a licensed PowerMTA into production: building it by hand, or renting a box by the month and hoping the setup behind it was done right.
| Route | Cost shape | What it really means |
|---|---|---|
| The Configurator | €799 once | Automates install, identities, DNS, dual-stack VMTAs, dashboard and 47 ongoing operations on your licensed PowerMTA. |
| Doing it by hand | Your time | Days of stack, DNS, VMTA, SSL and warm-up work — plus the deliverability cost of the mistakes made while learning. |
| Monthly managed SMTP | ~€80–€150+/mo | A recurring charge, often a shared or unclear licence, and another party holding the keys to your config. |
| PowerMTA licence itself | from ~$8,000/yr | The engine you bring — a separate vendor cost, not the server setup the Configurator handles around it. |
Read down that table and the case makes itself. A one-time €799 against days of your own time and the deliverability you'd burn learning on a live list; or against a monthly charge that never ends and a configuration you don't fully control. The cheapest-looking option — a low monthly server — is usually the one where you find out, three months in, that the warm-up was rushed or the reverse DNS was never set, and your IPs are already paying for it. Buying the configuration done correctly, once, is the move that protects everything you send afterwards. For the full side-by-side against running it yourself or moving to a hosted ESP, see Configurator vs DIY vs SaaS.
Who runs it
Matched to how you send
For ESPs & bulk senders
Multi-tenant sending across many domains and clients, each reputation isolated.
See the solution →For SaaS & transactional
Receipts, resets and verification codes that have to reach the inbox, kept apart from marketing.
See the solution →For agencies
Sending for clients with each reputation isolated, results proven, and onboarding in a command.
See the solution →For newsletters & publishers
Large recurring editions paced per provider, each title on its own IP group.
See the solution →Native integrations
Wired into the tools you already use
Why it's different
Built like infrastructure, not a wizard
Dual-stack architecture
Independent IPv4+IPv6 pools per domain with intelligent routing per destination provider.
Multi-client isolation
Separate domains, IPs, credentials, dashboards, suppression and alerts per client on one server.
Zero panel dependencies
No cPanel or Plesk — runs directly on the OS, so no license costs or resource overhead.
Auto-repair
Detects and fixes downed IPs, stopped services, bad permissions, expired SSL and lost firewall rules.
Deterministic config
The same domains file always produces the same config — reproducible, auditable, versionable.
A word on what the Configurator deliberately is not. Search for a PowerMTA installer and you'll find tools that advertise the engine "without a licence" or promise "unlimited" sending. Those rest on cracked software and the kind of volume that gets entire IP ranges blocked — a fast way to lose money and reputation at once. The Configurator takes the opposite position on purpose: it requires your own valid licence and automates legitimate, permission-based sending. The whole design assumes you want to send well for a long time, not blast a list once and rebuild after the block.
Straight talk
Everything here automates good practice for permission-based, opt-in sending: real authentication, isolated reputations, adaptive throttling that respects each provider's limits, and honest warm-up. Dual-stack pools, failover and per-ISP routing are about resilience and correct delivery — not evading filters or limits. The Configurator needs your own valid PowerMTA license, and it won't help send unsolicited mail, "unlimited" volume, or anything designed to dodge spam filters.
Stand up your ESP server today
One-time $799, no monthly. Bring your PowerMTA license and let the Configurator do the rest — or have us run it with a managed service. Sending across many clients? See solutions by use case.
Configurator FAQ
Is €799 really a one-time price?+
Yes — €799 once, no monthly subscription. The Configurator works with PowerMTA 6.0r2, any PowerMTA 5.x, and KumoMTA (all versions) — for PowerMTA you bring your own valid license; KumoMTA is open-source and free. The Configurator automates the install, configuration and ongoing operation around the engine. We never bundle, resell or crack PowerMTA itself.
Do I need to buy a PowerMTA license separately?+
Only if you choose PowerMTA. PowerMTA is commercial software, so for it you bring your own valid license and the Configurator installs and configures that licensed copy. If you'd rather not buy a license, the Configurator also supports KumoMTA — open-source and free, with no license to purchase. Either way the €799 pays for the automation and the 47 ongoing operations, not for the engine. We never bundle, resell or crack PowerMTA, and we won't work with a nulled or 'no-license' copy.
Which operating systems are supported?+
A clean AlmaLinux 8/9, Rocky Linux 8/9, Debian 12/13, Fedora or Ubuntu server. No control panel such as cPanel or Plesk is needed or wanted; the Configurator runs directly on the OS, which keeps both the licence overhead and the resource footprint down.
How long does deployment actually take?+
Under an hour from a bare server to one that is authenticated and sending, in the typical case. The four phases run end to end without supervision, and the slowest part is usually waiting for DNS to propagate before Phase 2 verifies it — which the Configurator handles for you rather than leaving as a manual check.
How does it deploy a whole server so fast?+
It runs as a single script across four phases: Phase 0 installs the full stack on a clean AlmaLinux, Rocky, Debian, Fedora or Ubuntu box (your engine — PowerMTA or KumoMTA — plus Postfix, Dovecot, Nginx, Node.js, CSF firewall and dependencies); Phase 1 generates each domain's identity (DKIM 2048, SPF, DMARC p=reject, MTA-STS, TLS-RPT, IPv6 AAAA/PTR) and publishes it via the Cloudflare API; Phase 2 verifies DNS propagated correctly; Phase 3 applies the production PowerMTA, Postfix, Dovecot and Nginx config with dual-stack VMTAs, SSL and dashboards. A bare server is sending in under an hour.
How is this different from a €80–€150/month managed SMTP server?+
Two things: cost shape and ownership. A monthly server is a recurring charge you keep paying, and on many of them the PowerMTA licence is shared or unclear and someone else holds the keys to your configuration. The Configurator is a one-time €799, runs on a box you control with your own licence, and the configuration is yours — reproducible and auditable rather than a black box you rent.
How is the Configurator different from a managed service?+
The Configurator is the tool you run yourself; it automates the setup and the day-to-day operations on your server. A managed service is where we run that platform for you on an ongoing basis. They're two ways to get the same clean setup — pick the Configurator if you want to own and operate it, and the managed service if you'd rather hand off operations entirely.
Is this 'unlimited' or no-licence PowerMTA?+
No, and that distinction matters. Some tools advertise PowerMTA 'without a licence' or promise 'unlimited' sending; that rests on cracked software and the kind of volume that gets IP ranges blocked. The Configurator requires your own valid licence and automates legitimate, permission-based sending. It will not help send unsolicited mail or anything built to dodge spam filters.
What's the dual-stack IPv4+IPv6 routing about?+
Every domain runs independent IP pools on both protocols, and the Configurator routes by destination provider — sending to Gmail over IPv6 once reputation is established, with automatic fallback to IPv4. It also audits and repairs downed IPs without a reinstall and migrates a domain between IPs with no downtime. It's for resilience and correct routing, never for evading a receiver's limits.
What can the real-time dashboard show me?+
The Node.js dashboard, served over HTTPS per client, shows delivered, bounced and deferred volumes, queue depth, DNS status across all domains, blacklist status across all IPs, and live PowerMTA logs with filters — so problems surface as alerts (also pushed to Telegram) rather than after placement drops.
How does warm-up and reputation work?+
It integrates with MailReach via API for account warming (batch, custom sender, configurable port and prefix) and includes a progressive IP-warming scheduler, adaptive per-ISP throttling for Gmail/Outlook/Yahoo, seed-list inbox-placement testing, BIMI, and guided registration with Microsoft SNDS, Yahoo/AOL FBL, Apple Postmaster and Barracuda. Reputation is built on legitimate, opt-in sending — never shortcuts.
Which ESPs and integrations does it support?+
MailWizz is supported natively (delivery and bounce servers, CSV export, stats), and a SendGrid v3-compatible API gateway lets any ESP send through the server. Native integrations include Cloudflare, Let's Encrypt, MailReach, Telegram, OVH (IPv6 PTRs), Postfix, Dovecot, Nginx and CSF.
Can one server host multiple clients?+
Yes. A single server hosts multiple clients with fully separate identities — domains, IPs, SMTP credentials, dashboards, suppression and alerts are independent per client — which is exactly what agencies and internal ESPs need. Configuration is deterministic: the same domains file always generates the same config, so it's reproducible and auditable.
How do I buy it or ask a question?+
Email [email protected] and tell us how many domains and IPs you're planning to run. We'll confirm the fit, answer licence and server questions, and get you the Configurator. It's a one-time €799 with no recurring charge.
Weighing it against doing it yourself or a hosted ESP? See Configurator vs DIY vs SaaS. Looking for PowerMTA's own license cost? See PowerMTA pricing & license 2026.