Builds
Sizes the fleet for your volume, installs PowerMTA and MailerQ, writes the configs and sets up domains with DKIM signing keys and reverse DNS (PTR).
About MTA-Hub
MTAs and delivery · MTA-Hub
MTA-Hub the control center for PowerMTA and MailerQ
A control panel for your own email infrastructure. The Hub installs the MTA (the mail server software that actually sends email) on your servers, sets up domains, picks working proxies, warms up IP addresses, watches the queues and hands ready sending points to your email platform. Mail goes out directly from your nodes: the Hub manages and monitors, but no mail passes through it.
- Self-hosted, runs on your own server
- PowerMTA and MailerQ in one registry
- Four email platforms
- Interface: RU, EN, UK
01 / What it is
Not a mailing tool and not a delivery service
MTA-Hub is what your mailing tool runs on: servers, MTAs, domains, IP addresses and proxies, plus everything that happens to them day to day. The Hub takes over the manual work of a delivery admin and shows your whole fleet at once, not one server at a time.
Prepares
Warms up each “IP address + domain” pair to a plan, tests proxies from the node itself and exports sending points to your platform.
Watches
Queues, mailbox provider responses, bounce reasons and IP reputation. Policies react on their own, and every operation is logged.
02 / How it works
Five steps from task to controlled sending
The path is the same at any volume: first the estimate, then servers and domains, then warm-up — and only warmed-up addresses go to your email platform.
- 01
Specification
Your answers about volume and mailing type become an estimate: how many nodes, IP addresses and domains, what it will cost and which MTA fits the job.
- 02
Installation
The Hub checks the server, installs PowerMTA or MailerQ, builds the config and sets up domains with signing keys.
- 03
Warm-up
A plan for each “IP address + domain” pair, a daily queue, and slowing down when mailbox providers start rejecting mail.
- 04
SMTP export
Ready sending points go to your email platform in one action — with the warm-up limit attached.
- 05
Control
Queues, response codes, bounce reasons, reputation — and policies that react on their own.
03 / Manual work
How much work the Hub takes off your hands
“I have SSH and my own scripts” is the most common answer. Here is what that really means. The numbers were measured on a live production setup.
to install an MTA
on a bare server — instead of an hour by hand following a guide, every single time.
DNS records
for a fleet of 10 domains and 40 IP addresses. The Hub publishes them itself and checks that they are visible.
of proxies fit for email
53 out of 8,878 checks. Testing runs from the node itself, with no human involved.
of daily warm-up
that a person would otherwise run. In the Hub, it is a plan plus a nightly cycle for each mailbox provider.
04 / PowerMTA and MailerQ
Two MTAs in one registry
You choose an action, not a command for a specific MTA. The Hub handles the differences itself — and honestly shows what one of them can’t do.
PowerMTA
- config built from a template in the same format as Protosender;
- live snapshot from the MTA’s management interface;
- accounting stats from the node’s accounting files.
The same for both
- one shared list of operations with preview and log;
- a health score from 0 to 100 at four levels;
- domains, signing keys, warm-up and proxies;
- export to any of the four email platforms.
MailerQ
- database, message broker and MTA are installed piece by piece;
- changes to the control database — no restart needed;
- snapshot taken from the broker queues, since there is no status endpoint.
05 / Modules
What’s inside
The panel is split by task. Each module has its own page with screenshots of the demo account.
Planning
Works out nodes, IP addresses, domains and the cost estimate for your volume — with the formula behind every number.
SpecificationsInstallation and nodes
An MTA on a bare server, node cards, reverse DNS checks, hosting providers and the infrastructure diagram.
MTA installationConfigs and policies
Config building with preview and rollback, plus response rules with a cool-down and an action limit.
ConfigurationsDNS and keys
Domain records, DKIM keys, your own name servers and checking zones against the plan.
DNSProxy Gate
Five acceptance stages run from the node itself, proxy pools, replacement rules and the gate that connects the MTA to the proxies.
Proxy GateWarm-up
Plans, a warm-up audience that knows the real provider behind each recipient’s mailbox, and an email library with spintax.
Warm-upMonitoring and analytics
A live snapshot of nodes, queue management, breakdowns by mailbox provider and PowerMTA accounting stats.
MonitoringPlatforms and export
Connect email platforms in two steps and export sending points with feedback coming back.
Platforms06 / Boundaries and data
What the Hub doesn’t do — and what stays with you
The Hub doesn’t stand between you and mailbox providers, and it doesn’t take your data. That’s not a promise — it’s how the product is built.
The Hub doesn’t
- send mail itself — the MTA on your nodes does;
- run your mailings: campaigns, lists and templates stay in your platform;
- store recipient contacts or email content;
- act as an email service: no shared addresses, no borrowed reputation;
- replace your PowerMTA or MailerQ license.
Stays with you
- the panel, nodes, credentials and signing keys — on your servers;
- secrets are stored encrypted, only a mask is ever shown;
- the Hub reaches your platform’s database over that server’s SSH, not through an open port;
- from the platform it takes only daily engagement counters;
- two-factor login and an activity log — you can see who did what;
- accounts are isolated: one customer can’t see another’s data.
07 / Questions
Questions about MTA-Hub
Didn’t find an answer? Email site@mta-hub.com or message us on Telegram.
Is it a cloud service?
No, it’s self-hosted. The Hub is installed on your server with a web installer — environment check, database, migrations, admin account — and everything it knows stays with you.
How much does MTA-Hub cost?
Prices and license options are on one page — Pricing. PowerMTA and MailerQ licenses are bought separately.
Which MTAs are supported?
PowerMTA 6 and MailerQ 5.16 — in one registry, with shared operations. How they differ and which to pick is on the PowerMTA vs MailerQ page.
Which email platforms does the Hub work with?
Protosender, Interspire, Mumara and MailWizz: the Hub gives them sending points and gets engagement counters back. Details are on the Integrations page and in the platform comparison.
Does the Hub need AI to work?
No. The plan is calculated with formulas, configs are built from presets, and warm-up runs on your own emails — without a single outside call. Right now AI Core is used to generate warm-up emails; an AI audit of your infrastructure is planned.
What does the Hub look like inside?
Screenshots of every page of the panel on demo data are in the Modules section: what’s on screen and what it’s for.
08 / Next step
Start with an estimate
Work out what your task needs: nodes, IP addresses, domains and a cost estimate. The estimate commits you to nothing — and then the Hub builds everything from it.
What you’ll need
- 01A server for the Hub panelThe panel is installed on it with a web installer.
- 02Servers for the nodesThe Hub will install PowerMTA or MailerQ on them.
- 03An MTA licensePowerMTA or MailerQ — separate from the Hub.
- 04Sending domainsThe Hub sets up DNS records and signing keys itself.
- 05An email platformProtosender, Interspire, Mumara or MailWizz.