Lists and subscribers
Lists and custom fields of seven types, segments, and signup forms with single or double opt-in.
Interspire
Email platforms · Interspire
Interspire and MTA-Hub a classic email platform on your own infrastructure
Interspire Email Marketer is a proven email platform that runs on your server: lists, campaigns, autoresponders, stats. The MailCore bundle adds Maborak modules and an AI layer to it. MTA-Hub runs everything underneath — PowerMTA and MailerQ nodes, domains, warm-up — and hands Interspire ready-to-use sending points.
- Sending points with no manual setup
- Warm-up limit sent with each SMTP
- One unsubscribe list
- PowerMTA and MailerQ nodes
01Interspire Email Marketerlists, campaigns, autoresponders, stats
02Maborak modulesMTA groups, multi-threading, bounces and complaints, spins
03AI layeremails, series and spam checks
04MTA-HubPowerMTA and MailerQ nodes, domains, warm-up, sending pointsinfrastructure
01 / The platform
What is Interspire Email Marketer?
One of the best-known self-hosted email platforms. Simple inside and predictable under load — that’s why people still choose it when steady high-volume sending matters most. The interface is available in Russian and English.
Campaigns and automation
Scheduled campaigns, split tests, autoresponders and emails triggered by subscriber actions.
Stats
Opens, clicks, bounces and conversions, per-link breakdowns and audience geography.
Team and API
Users and groups with per-section permissions, an action log, and REST and XML APIs for your own integrations.
02 / The MailCore bundle
Interspire, Maborak modules and AI — three layers of one system
The bare Interspire core is a good base, but it lacks tools for high volumes. In the MailCore bundle, those tools come from Maborak Technologies modules and an AI layer.
Multiple MTA + IP Monitor
Several SMTP servers and MTA groups with rotation, stats for each channel, IP address monitoring and PowerMTA support.
Multi-Thread
Multi-threaded sending from the command line: a large campaign goes out many times faster than through the regular queue.
Remote Bounce Processor
Bounce processing by your own rules: non-existent addresses are removed from the database before they hurt your reputation.
Feedback Loops
Complaints from mailbox providers in ARF format: whoever complains is unsubscribed automatically and gets no more emails.
Spins
Text spinning and rotation of subject, sender, reply-to address and links: every email goes out in its own version.
Geolocation Statistics and Backup
Where your audience lives — by country, region and city. Plus backups of the system itself.
The AI layer is the same six AI Core tools as in Protosender: offer analysis and funnel, emails and series, spam checks and spintax in Interspire format. The bundle, license and installation are handled by MailCore System.
03 / Multiple MTA and the Hub
Multiple MTA picks a channel. The Hub builds the channels.
The Maborak module spreads a campaign across the SMTP servers and vMTAs it’s given. Where they come from, how they’re configured, whether they’re warmed up and how mailbox providers accept them — that’s the Hub’s job.
Multiple MTA — inside Interspire
Works inside the email platform’s panel:
- rotates MTA groups and picks a channel for the campaign;
- counts stats for each channel;
- watches the IP addresses it sends through;
- uses SMTP servers and vMTAs as they were configured.
MTA-Hub — underneath Interspire
Works with servers, domains and IP addresses:
- installs PowerMTA and MailerQ and builds their configuration;
- sets up domains: SPF, DKIM, DMARC, signing keys and reverse DNS (PTR);
- warms up IP addresses by plan and slows down on bounces;
- selects and checks proxies for sending;
- sees queues, response codes and bounce reasons on every node;
- hands Interspire ready sending points — with a warm-up limit.
04 / Integration
What the Hub does with Interspire
Campaigns, lists and emails stay in Interspire. The Hub works from its own side: it hands over sending channels, checks them against the platform and takes back only what the infrastructure needs.
Sending point export
Tick what to export — the Hub adds the sending points to Interspire itself: node address, port, credentials, and an hourly limit if the IP address is still warming up.
The limit grows with the warm-up
When a ramp-up step is done, the new limit goes to the platform without a manual “refresh”. An IP address that isn’t fully warmed up won’t silently switch to full volume.
Reconciliation with the platform
The Hub finds differences between what it exported and what’s in Interspire: changed points, points deleted there, and points added without the Hub.
Engagement and volume
Opens, clicks, unsubscribes, complaints and email count — for each sending point, per day. If the platform counted more emails than the MTA saw, that’s a finding, not a rounding error.
Unsubscribes work everywhere
Warm-up and campaigns go to the same list of real people. The Hub merges their suppression lists: someone who unsubscribes from a warm-up email won’t get your real campaign either.
Tracking on the nodes
The Hub sets up tracking domains and puts the tracking archive on the nodes — links and unsubscribes are served from the same place the email is sent from.
Connecting takes two steps: first the Hub only reads the installation and shows a plan of changes; it writes after you confirm. It works with the Interspire server over SSH. It doesn’t take contacts, lists or email content.
05 / Who it’s for
Who Interspire with the Hub is for
For those who want a simple, robust email platform, with infrastructure underneath that grows without manual server work.
High volumes
Millions of emails a month, several nodes and IP pools. Interspire sends; the Hub runs the fleet and shows how mailbox providers accept its mail.
A marketer without a sysadmin
The marketer runs campaigns in Interspire on their own. Servers, domains and warm-up live in the Hub panel — no editing configs in a terminal.
Moving off a SaaS service
The same lists and campaigns, without paying per subscriber. The Hub sets up nodes and domains and warms up IP addresses before the big campaigns start.
Already on Interspire
The Hub connects to a running installation. SMTP servers set up earlier stay in place — reconciliation shows them as untracked.
06 / Questions
Questions about Interspire and the Hub
Didn’t find your answer? Email site@mta-hub.com or message us on Telegram.
Why do I need the Hub if Interspire has Multiple MTA?
They do different jobs. Multiple MTA spreads a campaign across the channels it’s given. The Hub creates and maintains the channels themselves: it installs the MTA, sets up domains and DKIM signing, warms up IP addresses and watches how mailbox providers accept them.
What does the Hub take from Interspire?
Only daily counters for each sending point: opens, clicks, unsubscribes, complaints and volume. Contacts, lists and email content stay in Interspire.
Does the Hub now process bounces and complaints?
No, Interspire with the Maborak modules still processes them: the list is cleaned where it lives. The Hub looks at bounces from the MTA side — for PowerMTA nodes it shows them by category, recipient domain and vMTA, so you can see where the problem is: in the list, in the email, or in the sending IP address.
Can I connect an Interspire installation that is already running?
Yes. First the Hub only reads the installation and shows what it’s going to change; it starts writing after you confirm. It doesn’t delete SMTP servers set up earlier — reconciliation shows them as untracked.
Does it work with MailerQ?
Yes. The Hub exports sending points from both PowerMTA and MailerQ nodes. For Interspire they’re sending channels, and the warm-up limit gets through in both cases.
What happens to my campaigns if the Hub is down?
Campaigns keep going out: Interspire sends straight to your nodes, and mail never passes through the Hub. Only the Hub’s own tasks wait — warm-up steps, stats collection and checks.
07 / Next step
Put your own infrastructure under Interspire
The Hub installs on your server, sets up nodes and domains, and hands Interspire ready sending points. Don’t want to build it yourself? We’ll deploy everything turnkey, including PowerMTA and warm-up.
What you’ll need
- 01A server for the Hub panelThe panel is installed on it with a web installer.
- 02Servers for nodesThe Hub will install PowerMTA or MailerQ on them.
- 03Interspire and SSH access to its serverSo the Hub can connect the platform.
- 04Sending domainsThe Hub sets up DNS records and DKIM keys itself — through your DNS provider or your own name servers.
- 05An MTA licensePowerMTA and MailerQ are licensed separately from the Hub.