MTA-Hub overview
Demo
Demo

Protosender

Email platforms · Protosender

Protosender and MTA-Hub campaigns and sending on your own servers

Protosender is an email marketing platform: lists, campaigns, automation and AI content. MTA-Hub prepares the sending side for it: it installs PowerMTA and MailerQ on your nodes, sets up domains, warms up IP addresses, and adds ready-to-use SMTP sending points to Protosender.

How they work together Protosender on MailCore System
  • SMTP export in one action
  • Warm-up limits sync automatically
  • Unsubscribes go to one shared list
  • PowerMTA and MailerQ nodes
Protosender · Delivery servers
203.0.113.21 : 2525 news@sender-a.com PowerMTAlimit 41 per hour · warm-up
203.0.113.22 : 2525 info@sender-a.com PowerMTAno limit
198.51.100.40 : 2525 mail@sender-b.net SMTP · MailerQlimit 12 per hour · warm-up
Example: sending points the Hub adds to Protosender. Addresses and domains are made up.

01 / The platform

What is Protosender?

An email marketing platform that you install on your own server. Your contact database stays with you, and your sending volume is limited by your own infrastructure — not by someone else’s plan.

Lists and segments

Unlimited lists, segments by fields and behavior, imports with duplicate cleanup. The platform handles unsubscribes, bounces and complaints on its own.

Campaigns and automation

Scheduled campaigns, event-triggered email sequences, and A/B tests of subject, content and send time that pick the best version.

AI tools

Six AI Core tools: offer analysis, funnel building, single emails and whole series, spam-trigger checks and spintax variations.

Sending strategies

The adaptive strategy keeps a pool of emails and a pool of SMTP servers. When an email or an SMTP server burns out, it is replaced separately for each mailbox provider, so the campaign keeps running.

Protosender and MTA-Hub come from the same developer, AI Core System. Licenses, installation and the full platform description are on the MailCore System website.

02 / How they work together

The Hub prepares sending. Protosender sends.

The split is simple: servers, domains and IP addresses are the Hub’s job; emails and subscribers stay in Protosender. After the export, the Hub doesn’t touch your campaigns: it runs the infrastructure and watches how mailbox providers accept it.

  1. 01

    Nodes

    The Hub installs PowerMTA or MailerQ on your servers — about six minutes per server — and builds the configuration.

  2. 02

    Domains

    SPF, DKIM and DMARC records, DKIM signing keys and reverse DNS (PTR) for every sending IP address.

  3. 03

    Warm-up

    A plan for every “IP address + domain” pair: a daily queue, growth along a curve, and slowing down when bounces appear.

  4. 04

    Export

    Sending points appear in Protosender as ready delivery servers — with credentials and a warm-up limit.

  5. 05

    Monitoring

    Queues, response codes, bounce reasons and IP reputation. Policies react on their own.

Emails go straight from your nodes: mail never passes through the Hub, and the Hub is not in the delivery path.

03 / Integration

What the Hub does inside Protosender

The Protosender integration is the deepest one: the Hub writes to its tables in the platform’s own format and uses the platform’s own access mechanisms — everything the Hub sets up is visible in the Protosender interface.

Sending points as delivery servers

PowerMTA nodes arrive in Protosender as PowerMTA-type servers, MailerQ nodes as regular SMTP servers. The sender domain always comes from the sending point’s address.

An IP address, a pool or proxies

You can export a single IP address, a node’s whole pool, or a proxy pool. A proxy pool has its own login, and Protosender sends through the proxies.

Warm-up limit

The hourly limit is calculated from the plan’s daily limit and rewritten in Protosender automatically after each ramp-up step. A limit on an IP address that isn’t fully warmed up can’t be silently removed — a person makes that call.

Reconciliation

The Hub compares what it exported with what is in the platform and shows changed records, records deleted in Protosender, and untracked ones — added there without the Hub.

Engagement and volume

Opens, clicks, unsubscribes, complaints and volume — per sending point, per day. The platform’s volume is checked against what the MTA saw, and low engagement stops the warm-up from growing.

Shared suppression list

An unsubscribe from a warm-up email counts in your real campaigns, and the other way around. Lists are merged per platform account; other accounts are not affected.

Tracking

The Hub sets up tracking domains and puts a copy of the tracking archive on the nodes: links and unsubscribes work from the same place the email is sent from.

Connecting without surprises

Read-only first: the Hub finds the installation, reads its configuration and shows a plan of changes. It writes only after you confirm. It reaches the platform’s database through that server’s SSH and Protosender’s own access registry.

The Hub doesn’t take contacts, lists or email content from Protosender.

04 / When you need the Hub

Protosender has its own PowerMTA module. Why do you need the Hub?

The Protosender module connects a PowerMTA server and sets up sending from the platform’s panel. You need the Hub when sending grows into a fleet of servers, IP addresses and domains that has to be watched every day.

The Protosender module is enough

If your sending is small and rarely changes:

  • one or two PowerMTA servers;
  • one Protosender installation;
  • IP addresses and domains hardly change;
  • there’s almost nothing to warm up: the IP addresses are already working.

Time to add the Hub

If at least one of these is true for you:

  • you have so many nodes that you need one registry, monitoring and an action log;
  • MailerQ runs next to PowerMTA;
  • you send through proxies that need to be selected and checked;
  • dozens of IP addresses and domains are warming up — by plan, slowing down on bounces;
  • you need accounting stats: bounces, domains and speed for every vMTA;
  • you have several platforms or clients — each with its own isolated account.

05 / Who it’s for

Who needs Protosender with the Hub

Your own email service

Protosender manages clients, plans and quotas; the Hub manages the nodes, IP addresses and domains underneath.

How to build your own service

Agencies

Each client gets their own Hub account with their own IP addresses and domains. Accounts are isolated from each other.

Sending to your own list

Info products, online stores, media: regular high-volume campaigns without someone else’s limits or topic bans.

Already on Protosender

The Hub connects to a running installation. It leaves existing delivery servers alone — reconciliation shows them as untracked.

06 / Questions

Questions about Protosender and the Hub

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

Where can I buy Protosender?

Licenses, installation and the full platform description are handled by MailCore System — the same developer’s site for email platforms. MTA-Hub is licensed separately; see the Pricing page.

Do I need the Hub if Protosender has its own PowerMTA module?

Not always. For one or two PowerMTA servers, the platform’s module is often enough. You need the Hub when you have many nodes, when MailerQ runs next to PowerMTA, when you send through proxies, or when dozens of IP addresses have to be warmed up by plan.

What does the Hub take from Protosender?

Only engagement counters for each sending point, per day: opens, clicks, unsubscribes, complaints and volume. Contacts, lists and email content stay in the platform.

Can I connect a Protosender installation that is already running?

Yes. First the Hub only reads the installation and shows a plan of changes; it starts writing after you confirm. The Hub doesn’t delete delivery servers added in the platform earlier — reconciliation shows them as untracked.

Does the Hub need access to the Protosender server?

Yes. The Hub reaches the platform’s database through that server’s SSH, not through a database port open to the internet. Access is granted through Protosender’s own registry, so you can see it in the platform’s interface.

Does it work with MailerQ?

Yes. MailerQ nodes arrive in Protosender as regular SMTP servers, PowerMTA nodes as PowerMTA-type servers. The warm-up limit reaches the platform in both cases.

What happens to my campaigns if the Hub is down?

They keep going: emails go from Protosender straight to your nodes, and the Hub isn’t on that path. Only the Hub’s own tasks pause — warm-up steps, stats collection and checks — until it’s back.

07 / Next step

Connect Protosender to your infrastructure

The Hub installs on your server, connects your nodes and adds ready sending points to Protosender. Need help getting started? We can 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. 03Protosender and 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.