MTA-Hub overview
Demo
Demo

Mumara

Email platforms · Mumara PRO + ESP

Mumara and MTA-Hub your own campaigns and your own service on your own fleet

Mumara is an email platform with split tests, triggers and multi-SMTP built in, and its ESP edition lets you launch your own email service. MTA-Hub runs the fleet underneath: PowerMTA and MailerQ nodes, domains, warm-up — and hands Mumara ready-to-use sending points.

The PowerMTA module and the Hub Mumara on MailCore System
  • SMTP export to Mumara
  • Warm-up limits sync automatically
  • One shared unsubscribe list
  • PowerMTA and MailerQ nodes

Your service’s clients

Shoe storeOnline schoolTravel agency37 more

campaigns in their own accounts

Mumara ESP

SMTP group “Marketing”“Transactional”“New clients”

sending points from the Hub

MTA-Hub · your nodes

PowerMTA · 24 IPsPowerMTA · 16 IPsMailerQ · 8 IPs
Example: your own email service on Mumara ESP. Names and numbers are made up.

01 / The platform

What is Mumara?

A self-hosted platform for high volumes where the professional toolkit isn’t sold as add-on modules: it’s there from the start. You can send through your own SMTP servers, an external delivery service, or PowerMTA. The interface is available in Russian and English.

Everything built in

Split tests, triggers, dynamic content, geo analytics, forms and autoresponders — all in the base package.

Up to 500 threads

Parallel campaigns with their own lists and SMTP servers. You set how many emails go through a channel before it switches to the next one.

Multi-SMTP

Unlimited SMTP servers and groups. Each channel has its own bounce server, FBL and link domain.

Blacklists

Mumara checks IP addresses and domains against blacklists and switches off any channel that lands on one.

02 / Two editions

PRO is for your own campaigns. ESP is for your own service.

Mumara is one of the few platforms that lets you not only send your own email but also sell sending as a service. The MailCore bundle includes both editions, version 2.35.

Mumara PRO

A platform for your own email marketing:

  • the full set of modules and threads, with no subscriber limits;
  • user groups with permissions — for your team and contractors;
  • your own projects: info products, a store, media, an agency.

Mumara ESP

The base for a commercial email service:

  • clients work in their own accounts on your domain, under your brand;
  • permissions and limits by group — each client gets their own sandbox;
  • a separate portal for support: clients, their stats, SMTP, bounces and complaints;
  • client signup and suspension through WHMCS via API.

The bundled AI layer is the same six AI Core tools as in Protosender and Interspire. The bundle, license and installation are handled by MailCore System. How to build the whole service — see Your own email service.

03 / The PowerMTA module and the Hub

Mumara has a PowerMTA config generator. How is the Hub different?

The Mumara module builds the configuration of one server from your domains and IP addresses. The Hub runs the whole fleet: from a bare server to a warmed-up IP address, on PowerMTA and MailerQ at once.

The PowerMTA module in Mumara

Works from the email platform’s panel:

  • builds a PowerMTA config from domains and IP addresses;
  • prepares DNS records with DKIM keys — as files for your registrar;
  • uploads the configuration to the server;
  • shows PowerMTA status and logs.

MTA-Hub

Works with a fleet of servers, domains and IP addresses:

  • installs PowerMTA and MailerQ on bare servers — about six minutes per node;
  • keeps the fleet’s configurations and policies that react to bounces on their own;
  • publishes DNS records itself — through your DNS provider or your own name servers;
  • warms up IP addresses by plan, and the warm-up limit reaches Mumara;
  • selects proxies and breaks down bounces by category, domain and vMTA.

04 / Integration

What the Hub does with Mumara

Campaigns, your service’s clients and their lists stay in Mumara. The Hub hands over channels, makes sure both sides see them the same way, and takes back only counters.

Sending points in Mumara

Single IP addresses or pools — you tick what to export. Along with the node address, port and credentials, the Hub sends an hourly limit if the IP address is still warming up.

Limits without manual edits

After each ramp-up step, the Hub raises the limit in Mumara itself. Only a person can switch an IP address that isn’t fully warmed up to full volume.

Channel reconciliation

Sending points changed in Mumara, deleted there, or added without the Hub show up right away — no silent mismatch between the systems.

Engagement per channel

Opens, clicks, unsubscribes, complaints and volume — for each sending point, per day, with volume checked against the MTA’s own data.

Shared suppression list

Someone who unsubscribes from a warm-up email won’t get your campaign either. The Hub merges warm-up and campaign lists within one platform account.

Tracking domains

The Hub sets up link domains along with their records. Mumara’s tracking lives inside its own installation, so no separate archive on the nodes is needed — that’s how the platform works.

Connecting takes two steps: first read-only access and a plan of changes, then writing. The Hub works with the Mumara server over SSH. It doesn’t take your service’s clients, their lists or emails.

05 / Who it’s for

Who needs Mumara together with the Hub

When a regular email tool is no longer enough: many clients, many servers, industrial volumes.

Industrial volumes

Hundreds of threads in Mumara and dozens of IP addresses on the nodes. The Hub shows how mailbox providers accept each IP address.

Agencies

Projects are split into groups in Mumara, and their IP addresses and domains into isolated Hub accounts.

Already on Mumara

The Hub connects to a running installation. SMTP servers added earlier stay — reconciliation shows them as untracked.

06 / Questions

Questions about Mumara and the Hub

Didn’t find your answer? Email site@mta-hub.com or message us on Telegram.

Mumara has its own PowerMTA module — why do I need the Hub?

The Mumara module builds the configuration and DNS records for a PowerMTA server. The Hub runs the whole fleet: it installs the MTA on bare servers, keeps PowerMTA and MailerQ in one registry, publishes DNS records itself, warms up IP addresses by plan, selects proxies and breaks down bounces for every node.

Is this setup good for running my own email service?

Yes, that’s its strong side. Mumara ESP manages clients, their permissions and limits. The Hub runs the nodes and IP addresses under the service and hands over sending points — as single IP addresses or pools — and Mumara assigns them to clients.

What does the Hub take from Mumara?

Only daily counters per sending point: opens, clicks, unsubscribes, complaints and volume. Your service’s clients, their lists and emails stay in Mumara.

Why doesn’t Mumara need a tracking archive on the nodes?

Mumara’s link and unsubscribe tracking lives inside its own installation. There’s no reason to copy it to the nodes: this isn’t a gap in the integration, it’s how the platform is built. The Hub still sets up the tracking domains.

Does the Hub need access to the Mumara server?

Yes: the Hub works with the platform through that server’s SSH, not through a database port open to the internet. It only reads at first and shows a plan of changes; it writes after you confirm.

Does it work with MailerQ?

Yes. Mumara works with both PowerMTA and MailerQ, and the Hub hands it sending points from nodes of both MTAs. The warm-up limit gets through in both cases.

07 / Next step

Put your own fleet under Mumara

The Hub installs on your server, sets up nodes and domains, and hands Mumara ready sending points. Launching an email service? We’ll build the infrastructure for you, turnkey.

Choose a license Turnkey infrastructure

What you’ll need

  1. 01A server for the Hub panelThe panel is installed on it with a web installer.
  2. 02Servers for nodesThe Hub will install PowerMTA or MailerQ on them.
  3. 03Mumara and SSH access to its serverSo the Hub can connect the platform.
  4. 04Sending domainsThe Hub sets up DNS records and DKIM keys itself — through your DNS provider or your own name servers.
  5. 05An MTA licensePowerMTA and MailerQ are licensed separately from the Hub.