On-premise MTA setup, done right the first time.
We install and configure your on-premise MTA (GreenArrow Engine, Halon, KumoMTA, Postfix, PowerMTA and others), then guide you through warm-up until it’s sending at full volume, with an earned reputation and mail reaching the inbox.
Trusted by teams that want control over email delivery.
Where MTA setups go wrong
You want to run your own sending infrastructure, or your current MTA is outdated and needs replacing. The move is where many problems start.
Your technical team can handle it
Often they can, but it takes months of trial and error that we’ve already been through.
You’d rather focus on your product
We handle the infrastructure so your team doesn’t have to learn it from scratch.
You tried it before and it went badly
Most failed setups come down to poor configuration or a rushed warm-up. We do both properly.
Ongoing maintenance takes a lot of effort
It shouldn’t. A well-configured MTA needs far less attention than a poorly deployed one.
We agree a project plan, design the system architecture and prepare a clean MTA configuration. We check the reputation of your existing IPs and advise whether new ones are needed. We prepare feedback loops and bounce processing, and draft your IP warm-up and volume migration plan.
We install and configure the MTA, then connect it to your systems, from email injection to bounce processing. An end-to-end test confirms everything works before we touch live volume.
We increase your sending volume gradually, monitoring results and adjusting the MTA configuration as real traffic passes through it. By the end of warm-up, you’re sending at full volume with a reputation you’ve earned. How long that takes depends on your volume and how engaged your recipients are.
Expert support to design, deploy and operate your email infrastructure.
On-premise setup covers everything from system design to the final warm-up, for any MTA. This is the scope of the engagement:
- System architecture and MTA installation
- Configuration and integration setup
- Feedback loop and bounce processing
- End-to-end delivery testing
- IP-warming and volume migration plan
- Continuous monitoring and tuning during warm-up
Included: training
Your team gets hands-on training for both super users and day-to-day operators, plus written documentation: a cookbook you can return to whenever a question comes up.
Built for reliable email delivery
Production-ready infrastructure, configured for performance and deliverability
- Smoother deliverability from day one
- Faster, better-tuned warm-up
- Fewer deferrals and blocks
- Reputation preserved during migration
- A documented system your team can run
For whom?
Brands moving to on-premise
You’re bringing sending in-house for control or cost. We handle architecture, installation and warm-up so your first campaigns don’t pay for a rushed migration.
Agencies standardising infrastructure
You manage sending for multiple clients and need infrastructure that’s consistent and documented. We set up a system your team can operate and hand over cleanly.
ESPs adding or replacing an MTA
You’re scaling volume or replacing an ageing MTA. We configure for your specific throughput and provider mix, not a generic template.
Teams migrating to new vendors
You’re moving from one MTA to another and can’t afford to lose sending reputation. We translate settings and manage warm-up so your history carries over.
Trusted by the teams who know
From delivery engineers to CTOs, here’s what the teams we work with have to say.
"A real WIN-WIN" | Ken O'Droscoll, Head of Deliverability - Upland Software
Your questions answered
We support GreenArrow Engine, Halon, KumoMTA, Postfix, PowerMTA and others. As a vendor-independent integrator, we recommend and configure whichever MTA fits your volume and team, and connect it to the Postmastery Console for monitoring from day one.
A full MTA setup typically takes ten to twenty weeks from kick-off to full sending volume. The first two weeks cover architecture and configuration, weeks three and four cover installation and testing, and the remaining weeks cover monitored warm-up. The exact timeline depends on sending volume and recipient engagement.
Yes, DNS and authentication are part of every setup. We configure SPF, DKIM and DMARC alongside the MTA itself, and align feedback loop and bounce processing so the full delivery chain works before volume migration starts.
Yes, migrating between MTAs is one of the most common reasons clients come to us. We translate your existing configuration to the new platform and manage warm-up in stages, so your sending reputation carries over instead of resetting.
Pricing depends on the number of MTAs, your sending volume and how much of the warm-up needs active tuning. Contact us for a quote based on your setup.
We require remote access to your infrastructure, using SSH for Linux systems or RDP for Windows, along with details about your existing setup, IP allocation and sending volume. We will confirm the complete requirements checklist with you at kick-off, before any configuration work begins. If your security guidelines call for it, we can also set things up via screen sharing instead.