How many messages reached the MTA?
Comparing volumes helps you spot gaps between your platform and your infrastructure.
- Platform
- 10,000
- MTA
- 9,850
- Difference
- 150
Example check. The numbers are illustrative.
Integrations
MTA-Hub integrations
Your campaigns stay in your platform.The Hub runs the infrastructure.
Connect ready SMTP servers and get feedback from your platform.Campaigns, lists and messages stay in your email platform.
Protosender, Interspire, Mumara and MailWizz — all with the same set of operations.
01 / Export and sync
Ready SMTP —
in your platform
Pick the sending points you need. The Hub creates them in your platform and passes on the connection details along with the hourly warm-up limit.
Protosender, Interspire, Mumara and MailWizz
How sender details are saved
The sender domain is taken from the sending address. If there is no domain, the Hub explains the error.
An empty sender name means “leave as is”: the existing value is kept when you update.
MTA-HubProtosender
- 01 Node address
203.0.113.10- 02 Port
2525- 03 Credentials
- Username and password
- 04 Warm-up limit
- Sent along with the SMTP details
The settings reach your platform without copying them by hand.
After export — a check
The Hub compares its records with what is in your platform.
- Changed
- The settings in the platform differ.
- Missing
- An exported record has been deleted.
- Untracked
- The SMTP connection exists in the platform but not in the Hub.
02 / Feedback
See the results.
Control the pace.
Your platform sends back daily counts for every sending point. The Hub compares them with MTA data and uses engagement to steer the warm-up.
- Opens
- Clicks
- Unsubscribes
- Complaints
- Volume
Warm-up takes engagement into account
If engagement drops below the threshold set in the plan, the Hub stops the volume from growing further.
Low engagementGrowth paused
In development Building a warm-up audience from people who open messages or click links in your platform.
Campaign lists and message content are never imported. Unsubscribes have their own exchange — a shared suppression list.
03 / Shared suppression list
One unsubscribe
counts in both flows
The Hub merges the suppression lists (addresses you must not mail) for warm-up and campaigns within one platform account. An unsubscribe from a warm-up message also counts in your real campaigns.
- Shared at
- Platform account level
- Boundaries
- Other accounts are not affected
Warm-up
Campaigns
Shared suppression listUnsubscribes count across both
At the account level — wide enough to cover warm-up and campaigns, while keeping clients separate.
04 / Tracking
Domains and links —
part of your infrastructure
The Hub sets up tracking domains (for opens, clicks and unsubscribes) and puts a copy of the tracking archive on your nodes. For Protosender and Interspire, it handles the whole path.
- 01
Tracking domains
The Hub prepares the domains that links and unsubscribes run on.
- 02
Archive on the nodes
A copy of the tracking archive is placed in your sending infrastructure.
- 03
Links and unsubscribe
They work from the same place the matching node sends from.
No archive needed
Mumara and MailWizz handle tracking inside the platform itself.
05 / Connection
Check first.
Then change.
Connecting takes two steps. Before writing anything, the Hub shows you a plan of the changes it will make.
- 1Read only
Discovery and plan
- Find the installation by its panel address
- Read the configuration and test the connection
- Show which changes will be needed
- 2Write
Access setup
- Create a separate user for tracking
- Allow access from the tracking nodes’ addresses
- Use the platform’s own access registry
The database connection goes through SSH on the platform’s server. You don’t need to open the database port to the outside. MailWizz connects with an API key — it needs no server login.
06 / Platform support
What’s available
for your platform
All four integrations use the same set of operations; the only differences come from how each platform is built.
“Not needed” reflects how the platform works, not an unfinished feature.
| Feature | ProtosenderAvailable | InterspireAvailable | MumaraAvailable | MailWizzAvailable |
|---|---|---|---|---|
| SMTP export | Available | Available | Available | Available |
| Sync | Available | Available | Available | Available |
| Tracking domains | Available | Available | Available | Available |
| Tracking archive | Available | Available | Not needed | Not needed |
| Engagement | Available | Available | Available | Available |
| Suppression list | Available | Available | Available | Available |
| Access to the panel server | Needed · SSH | Needed · SSH | Needed · SSH | Not needed · API |
ProtosenderAvailable
- SMTP export
- Available
- Sync
- Available
- Tracking domains
- Available
- Tracking archive
- Available
- Engagement
- Available
- Suppression list
- Available
- Access to the panel server
- Needed · SSH
InterspireAvailable
- SMTP export
- Available
- Sync
- Available
- Tracking domains
- Available
- Tracking archive
- Available
- Engagement
- Available
- Suppression list
- Available
- Access to the panel server
- Needed · SSH
MumaraAvailable
- SMTP export
- Available
- Sync
- Available
- Tracking domains
- Available
- Tracking archive
- Not needed
- Engagement
- Available
- Suppression list
- Available
- Access to the panel server
- Needed · SSH
MailWizzAvailable
- SMTP export
- Available
- Sync
- Available
- Tracking domains
- Available
- Tracking archive
- Not needed
- Engagement
- Available
- Suppression list
- Available
- Access to the panel server
- Not needed · API
MailWizz works through the API. This integration doesn’t need access to the panel server.
07 / Who does what
Each system
does its own job
You keep working in your email platform. After export, the Hub runs the infrastructure, the warm-up and SMTP sync.
MTA-Hub
- Servers, PowerMTA and MailerQ
- Warm-up, limits and policies
- Monitoring, SMTP export and sync
Your platform
- Campaigns and sending schedules
- Lists and audience management
- Message content and design
The Hub installs the MTA and exports ready SMTP connections. Installing email platforms is not part of its job.