Deliverability,mySMTP Marketing

Running MailWizz on mySMTP: Warmup and Quota Tools for Better Deliverability

If you self-host MailWizz in Europe, the United States, or anywhere else, mySMTP can sit behind it as your dedicated SMTP relay, handling secure email delivery to Gmail, Outlook, Yahoo, Apple Mail, and other major mailbox providers while MailWizz manages your campaigns, subscribers, and templates.

The software stack is only part of the equation. The biggest factors affecting inbox placement are sending speed, IP warmup, minute-based throttling, and sender reputation. Even a perfectly configured MailWizz installation can suffer from spam-folder placement, higher bounce rates, temporary blocks, or reputation damage if a new IP ramps up too aggressively or if sending limits exceed what mailbox providers expect.

MailWizz intentionally leaves these delivery decisions to the administrator. Every delivery server includes a configurable Quota field, but it doesn't calculate the optimal warmup schedule, hourly pacing, or per-minute sending rate needed for safe, sustainable email delivery.

That's exactly where the mySMTP Warmup Schedule Generator and Minute Quota Optimizer help. Rather than connecting directly to the MailWizz , both tools act as intelligent delivery calculators. Simply enter your planned email volume, delivery server configuration, IP setup, and campaign goals, and they generate recommended warmup schedules, minute quotas, and sending limits based on email deliverability best practices. You then copy the recommended values into your MailWizz delivery server settings.

The result is a more predictable sending pattern, improved inbox placement, healthier IP reputation, lower complaint and bounce rates, and a delivery strategy that's easier to scale as your email volume grows.

Background
What MailWizz actually is
A quick primer for anyone evaluating it or onboarding a new team.

MailWizz has been around since 2013, built on PHP and MySQL, sold as a one-time license rather than a subscription — you install it on your own server and own it outright, with unlimited lists, subscribers, and campaigns. That self-hosted model means you're also responsible for keeping the server patched and running; there's no vendor doing it for you.

Feature-wise it's a full email marketing platform: drag-and-drop and HTML campaign editors, autoresponders, RSS-to-email, A/B testing, and per-campaign open/click/bounce reporting. It also supports multiple delivery servers side by side (SMTP, Amazon SES, SendGrid, and others), with its own SPF/DKIM configuration fields, bounce-server integration, and feedback-loop (FBL) processing for complaints. There's even a billing/customer layer for agencies reselling sending as a service.

What it doesn't do is tell you what a safe sending rate looks like — that depends on domain age, ISP mix, and risk tolerance, none of which MailWizz has visibility into. That's the open question these two tools help answer.

Warmup Schedule Generator
Builds a day-by-day IP/domain warmup ramp with weekly checkpoints

You give it a start volume (typically 50–200 for a brand-new IP), a target daily volume, email type, and domain reputation. It outputs a full ramp with a progression chart and CSV/JSON export — MailWizz has no equivalent of "day 14 of warmup," so this schedule is the missing piece you apply manually as the ramp progresses.

The Daily Volume column is what you translate into MailWizz: on each flagged checkpoint day, update the delivery server's hourly quota so that day's total fits your sending window. A Day 3 value of 110 emails over a 10-hour window is roughly 11/hour — comfortably safe for week one.

MailWizz has no field for pasting in a 28-day ramp. Most teams update the quota manually at each checkpoint, or write a small script against the exported JSON and MailWizz's API to patch the quota on schedule.
Minute Quota Optimizer
Turns IP count, ISP mix, and target volume into a safe per-minute quota

This one picks up where warmup leaves off — steady-state sending on an already-warm IP. Enter your ISP mix, IP count, and target volume, and it returns a comparison table of candidate quotas, each with a risk level and predicted bounce rate.

Pick a quota from the table and the tool renders it using MailWizz's exact field names — no unit conversion, no guessing which setting a number belongs to:

MailWizz setting path Admin panel navigation
Backend Servers Delivery Servers Edit server Quota settings
Hourly quota
2,700
Max emails/hour for this delivery server
Quota value
45
Emails/minute — MailWizz's minute quota field
Max connections
15
Parallel SMTP connections, ≈ quota ÷ 3
Connection delay (ms)
833
Delay between connection attempts
Quota is per delivery server, not per campaign. With multiple IPs, apply the same quota to each server individually — MailWizz enforces the limit per-server, independent of how many campaigns run at once.
Putting it together
A full MailWizz + mySMTP workflow
Used in sequence, the two tools cover a delivery server from Day 1 through full volume.
1
Size the target with the Quota Optimizer
Run it with your expected steady-state ISP mix and IP count to get the target volume to warm toward.
2
Generate the ramp
Set Starting Volume to 50–100, Target Daily Volume to step 1's number, mark new domains, and export the CSV.
3
Create the delivery server at Day 1 volume
Backend → Servers → Delivery Servers → Add new. Set Quota value to cover only Day 1 — don't pre-fill the target.
4
Step the quota up at each checkpoint
Update the quota on flagged checkpoint days. Keep the sending window consistent across both tools and MailWizz.
5
Re-run the optimizer, then trust MailWizz's live data
Once warm, re-check quota against your actual ISP mix. After that, let real bounce/complaint rates in MailWizz override the schedule if they climb.
Both tools are stateless — re-run the optimizer any time your ISP mix shifts meaningfully. A list moving from 40% to 65% Gmail changes the safe quota even if total volume hasn't changed.

Try both tools free

Part of the mySMTP Deliverability Toolkit — no signup, runs entirely in your browser.

Open the Toolkit →