MailWizz hosting

MailWizz hosting where the delivery servers are the point

MailWizz is a front-end. It builds campaigns, manages lists and tracks results, and then hands every email to a delivery server you configure. That delivery server is where deliverability is won or lost, and where most MailWizz setups fail. SendHaven provides the delivery servers: dedicated, authenticated, warmed, monitored and replaced when burned.

Keep
Your MailWizz install
Dedicated
IPv4 per delivery server
Minutes
To add as SMTP server
Replaced
When burned, included

Why MailWizz installs end up with deliverability problems

MailWizz is good software and it is almost never the reason email lands in spam. The reason is what sits behind it. Three patterns we see constantly:

  • Shared SMTP behind MailWizz. SendGrid, SES or Mailgun credentials in the delivery-server slot. Works until the first content review, then the account is closed and MailWizz has nowhere to send.
  • A single VPS doing everything. MailWizz, the database and the MTA on one box with one IP. One complaint spike blacklists the only IP you have, and the whole operation stops. More on why single-VPS setups burn.
  • Cheap SMTP from a reseller. Unknown IP history, no authentication on your domain, no warmup, gone in a month.

The fix is the same in all three cases: keep MailWizz, give it delivery servers that are dedicated to you, authenticated on your domains, warmed properly and replaced when they burn.

Adding SendHaven as a MailWizz delivery server

  1. In MailWizz, go to Servers, Delivery servers, Create new, choose SMTP.
  2. Enter the hostname, port, username and password we give you, with TLS enabled.
  3. Set the from domain to one of the sending domains we have authenticated, and set the hourly quota to the warmup figure in your onboarding sheet.
  4. Set bounce server and feedback loop handling, or leave suppression to us; we return bounce and complaint data to your platform.
  5. Assign the delivery server to customer groups or campaigns. Add one delivery server per SendHaven server to use MailWizz's own load balancing across them, or point at our single rotating endpoint.
  6. Send a test to a seed list. Check the headers for SPF, DKIM and DMARC passes. Start the warmup schedule.

Total time is under half an hour for someone who has used MailWizz before. We do it with you on the onboarding call if you prefer.

The MailWizz architecture that survives high-risk sending

Separate the three jobs:

  • Application: MailWizz and its database on a normal web host or VPS. It sends nothing itself, so it never gets blacklisted and can live anywhere.
  • Delivery: SendHaven dedicated servers, one IP each, rotated. This is the layer that takes the reputation hits and gets replaced.
  • Tracking: custom tracking domains (included on three-server plans and up) so clicks and opens run on your domains, not a shared tracker that gets flagged.

With this split a burned IP is a server swap on our side and a credential update on yours. The application, the lists and the history are untouched.

Lists. MailWizz will happily import anything. Verify before you import. Invalid addresses and spam traps are what burn delivery servers fastest.

Scaling a MailWizz operation on dedicated servers

Start with one server to validate your list and content. Move to three for rotation and redundancy, which is where most MailWizz operators settle, because losing one of three IPs is an inconvenience rather than an outage. Five servers for agencies running multiple customer groups, each group on its own delivery server, with the white-label dashboard on custom plans.

Adding a server is a new delivery server entry in MailWizz and nothing else. Removing a burned one is our job.

MailWizz delivery server pricing

Per server, flat. MailWizz itself is not included; you keep your own licence and install.

1 Server
Start lean, test your sending
€499/mo
  • 1 dedicated sending server
  • Dedicated IPv4 address
  • SPF / DKIM / DMARC setup
  • Server replaced when burned
  • SMTP & API access
Book a Call
Most popular
3 Servers
Rotation & redundancy built in
€1,297/mo
  • 3 dedicated sending servers
  • Round-robin IP rotation
  • IP warmup service
  • Priority support (24h)
  • Custom tracking domains
Book a Call
5 Servers
High volume & maximum resilience
€1,997/mo
  • 5 dedicated sending servers
  • Advanced rotation pools
  • Unlimited email volume
  • Dedicated account manager
  • Per-domain rotation strategy
Book a Call

No setup fees. No contracts. Card, bank transfer or crypto. Full feature comparison →

MailWizz hosting FAQ

No. We provide the delivery servers MailWizz sends through. The MailWizz application should live on a normal web host so it never shares an IP with your sending. We can recommend a setup on the call.

Yes. Nothing changes in your MailWizz install except the delivery server entries. Lists, campaigns, templates and tracking stay as they are.

Yes. Add each as its own SMTP delivery server and let MailWizz balance across them, or point MailWizz at our single rotating endpoint and let us balance. Both work; the first gives you more visibility in MailWizz, the second is simpler.

Bounce and complaint processing runs on our side and the data is available to your platform. If you prefer MailWizz to process bounces itself, configure a bounce server as usual; both approaches are supported.

Not if they run on your own custom tracking domains, which are included from the three-server plan. Shared tracking domains are a common and avoidable cause of spam placement.

Same setup: any platform with a custom SMTP delivery server option connects the same way. The instructions differ slightly per platform and we walk through them on onboarding.
Related

Tell us your volume and your vertical.

We'll come back with a server plan, a warmup schedule and a price. Servers live within 48 hours of sign-off.

Book a Demo

or email hello@sendhaven.io