MailWizz will install almost anywhere with PHP and MySQL. Whether it can actually deliver depends entirely on things the host controls, and most hosting pages never mention them. Here is what to check, including the questions we would rather you asked us.
3
Port 25 blocked · shared IP · no custom rDNS
MailWizz itself is undemanding — an ordinary Linux, PHP, MySQL and cron stack. What decides whether your campaigns land is the network underneath it: whether outbound Port 25 is open without an application, whether the IPv4 address is yours alone, and whether the provider will set a reverse DNS record to match your sending hostname. A host that fails any of those three cannot run MailWizz properly no matter how much CPU it sells you. Everything else is comfort.
Related: Running MailWizz on a VPS · All six packages compared · Port 25 · rDNS · SMTP VPS
The requirements come from the software vendor; the verdicts are ours and are answered straight. Where the answer is no, it is no.
| Requirement | Why it matters | Us |
|---|---|---|
| Outbound Port 25, open now | MailWizz can use a relay, but if you want your own SMTP server to be one of its delivery servers, Port 25 has to be open. Many hosts block it and some never unblock it. | Yes Open by default on every plan, no approval step |
| A dedicated IPv4 address | Sending reputation attaches to the IP. On a shared address you inherit the behaviour of everyone else using it, and you cannot set a meaningful PTR record. | Yes Included on all plans, no extra charge |
| Custom reverse DNS | Receiving servers check that the PTR record matches your sending hostname. Only the IP owner can set it, so a host that will not do this is a hard blocker. | Yes Set by support on request, free |
| Root access | MailWizz needs cron, specific PHP settings and often a local MTA. A managed panel that restricts these gets in the way. | Yes Every plan is unmanaged, full root |
| Fast storage for the database | Segmenting a large list and building campaign reports are read-heavy database operations. This is what you feel as the list grows, long before CPU matters. | Yes NVMe on NVMe VPS, Cloud VPS and VDS |
| Additional IPv4 addresses | Useful once you want to separate traffic types or rotate sending addresses. Worth asking about before you commit rather than after. | Yes Available — ask support for current options |
| IPv6 | Rarely essential for sending, since most receiving infrastructure still prefers IPv4, but worth knowing if your stack expects it. | Depends Varies by datacenter — ask about your location |
| Managed setup and tuning | Some senders want the host to install and configure the stack. That is a legitimate requirement, and it is not what we sell. | No All plans unmanaged; support covers platform, not your MTA |
| Backups of your subscriber list | A subscriber database is the one thing you genuinely cannot lose. Check who is responsible before you import anything. | No We hold no copy of your data on any plan — set up your own |
Sources, checked 17 August 2026
Read at each vendor's own documentation rather than taken from a summary. Follow the links and check for yourself — figures like these move.
Ask any provider, including us. The answers are more revealing than a feature list, and a vague reply is itself an answer.
Derived from the requirements above rather than from a price target. If your list or sending volume is unusual, ask us rather than guessing from this.
Segmentation and campaign reporting are database work; two cores and 4 GB handle real lists.
2 Cores · 4 GB RAM
40 GB NVMe · 10 Gbps Port
$17.95/mo
This is a starting point, not a rule — list size and sending frequency matter more than the software itself. See all plans · compare all six packages · ask before you order.
From $4.95 a month with root access from the first second, and a 7-day money-back guarantee if the fit turns out to be wrong.
