MTA-Hub overview
Demo
Demo

Features

MTA-Hub features

From your taskto workingSMTP infrastructure

Size your resources, set up your MTA and warm-up, and hand ready SMTP connections to your platform. Run your whole infrastructure from one panel.

Choose a license Plan your infrastructure
  • Runs on your own server
  • PowerMTA and MailerQ
  • Warm-up guided by mailbox provider responses
  • SMTP export to your platform

01 / Planning

A plan for your infrastructure

Answer a few questions about your mailings. The Hub prepares a specification you can use to buy and launch your infrastructure.

  1. Describe your task

    List size, mailing type and the mailbox providers you send to.

  2. Set your limits

    Launch date and available budget.

  3. Get a ready plan

    Resources, configurations, a cost estimate and launch stages.

Three ways to calculate

You have a task MTA-Hub recommendation
The Hub picks the server set and sending pace based on your list, niche and email sequence.
You have a target volume Limit sending per day
Set how much you want to send per day, and the builder works out the servers, IP addresses and domains.
You have a budget Budget limit
Enter an amount, and the Hub calculates the server set and shows what the budget allows and where it falls short.
How the Specifications module works
Ready plan MTA-HUB

Specification · example

Your infrastructure plan

Online store · own list · Europe

Nodes
PowerMTA or MailerQ
Sending points
SMTP for every address
Domains
for sending and tracking
Accounts
with different hosting providers
  • Node rentalmonthly
  • Domainsonce a year
  • Startup costsone month + domains
Launch stages List cleaning Warm-up Activation Segmentation Sales sequence
Download a sample specification PDFCSV
Example: the “Lumacart · marketing” plan from the demo account. Your numbers depend on your answers to the questionnaire; you can refine the plan and save it as versions.

02 / Infrastructure launch

Connect your servers.
Launch the MTA you need.

You give the Hub access to a server, and it does the rest: checks the node, installs PowerMTA or MailerQ, builds the configuration and sets up domains with DKIM signing keys.

  • ≈ 6 minutesto install on a clean server
  • 2 MTAsPowerMTA and MailerQ in one registry
  • 90 recordsDNS for 10 domains in one export
  • Task historyevery operation with the server’s responses

03 / Warm-up

Warm-up
under the Hub’s control

Set a plan for your addresses and domains. The Hub spreads out the sending and adjusts the limits based on how each mailbox provider responds.

How the daily limit changes

Illustrative example
Decision for one
mailbox provider from day 7
Limit, % of target volume
Example of how the warm-up limit changes Illustrative example: the plan ceiling keeps rising, while from day 7 the daily limit is held at the same level.
Hold

When results get worse, the Hub keeps the limit where it is and pauses growth.

  • Address and domain together

    The limit for each pair reflects how ready both the sending address and the domain are.

  • An even flow through the day

    Sending is spread across the time windows you set.

  • Limits go straight to the MTA

    The Hub recalculates them and pushes the new values to the node.

04 / SMTP export

Ready SMTP —
in your platform.

Ready sending points go to your email platform in one step, along with an hourly limit if the address is still warming up. Your campaigns and emails stay where they already are.

Export example

Infrastructure3 SMTP

MTA-Hub

Prepared connections

  • SMTP-01mail-01.example
  • SMTP-02mail-02.example
  • SMTP-03mail-03.example

Selected for export

Platform3 SMTP

Protosender

Connections in the platform

  • SMTP-01mail-01.example
  • SMTP-02mail-02.example
  • SMTP-03mail-03.example

Connections created

MTA-HubServers, MTAs, domains and warm-up.

ProtosenderCampaigns, audience and emails.

05 / Monitoring and control

Control continues
after launch

Node health, queues and bounce reasons in one panel. Act on it yourself, or set up a rule once and let the Hub do it for you.

Needs attention

Example situations

Pick a situation to see what happened and how you could respond.

Manual control

Queue is growing

PowerMTA · Node 01

  1. Signal

    Messages are piling up on the node.

  2. Check

    Queues and MTA responses by recipient domain.

  3. Response in this example

    Pause the selected queue once the cause is checked.

Manual action: preview first, then run it and record it in the log.

One set of actions for PowerMTA and MailerQ, adapted to what each MTA can do.

06 / Infrastructure growth

Grow your infrastructure
and stay in control.

Your fleet is already running? Add nodes, addresses and domains. The Hub checks them against the plan, shows any mismatches and gets the new resources ready to send.

Growth example

Current nodes

Node 01

PowerMTA

3 IPs · 3 domains

Running

Node 02

MailerQ

3 IPs · 3 domains

Running

Adding to the infrastructure

Node 03

PowerMTA

2 of 3 IPs · 3 domains

Check resources

Node 04

MailerQ

3 IPs · 3 domains

Connected

Mismatches show up on connection

In this example, node 03 has 2 of the 3 planned IPs connected. The Hub shows the difference so you can adjust the setup.

  • Several infrastructures

    Each project gets its own specifications and set of nodes, kept fully separate.

  • Teamwork

    Workspaces, roles and an activity log: split access and see who changed what.

MTA-Hub modules

See how it all
works inside

All twenty Hub modules in detail: what each one does, how it looks in the panel and which tasks it helps with.

Explore modules Choose a license