Every few weeks someone opens a ticket that starts the same way: "I set up Mailcow, everything works, but Gmail keeps sending my mail to spam." Nine times out of ten the software is fine. The problem lives one layer down — in the IP, the reverse DNS, and the reputation of the address space the mail leaves from. A self-hosted email server VPS is not really a software project; it is an infrastructure project wearing a software costume. This is our notes-from-the-rack take on what actually decides whether your mail lands.
Why run your own email server at all
The honest answer: for control and privacy, not to save a euro. Managed inboxes are cheap and convenient. But you don't control where the data sits, you can't audit the delivery path, and you can't move it. When you run your own email server on a VPS you get root, you get the full SMTP pipeline, and you decide the jurisdiction. For a small team, a family domain, or a business that wants its correspondence under its own roof, that trade is worth the maintenance tax. If you'd rather not, use a managed provider — there's no shame in it, and we'd tell you the same thing in a support ticket.
Mailcow vs Mail-in-a-Box: pick your stack
Two self-hosted stacks cover almost everyone. Mailcow is a Dockerised suite — Postfix, Dovecot, Rspamd, SOGo webmail, ACME certs — with a clean admin UI. It wants a bit more RAM and rewards you with per-domain controls, good spam filtering, and easy DKIM management. Mail-in-a-Box is the opposite philosophy: one script, opinionated defaults, minimal knobs. It runs Postfix, Dovecot, and Nextcloud contacts on a single box and is genuinely hard to misconfigure.
If you want a webmail and admin panel out of the box and expect to host several domains, Mailcow. If you want "install and forget" for one or two domains, Mail-in-a-Box. Either way you'll want headroom — a 2GB tier runs Mail-in-a-Box comfortably, but Mailcow's documented minimum is 6 GiB of RAM plus 1 GiB of swap, so pick an 8GB tier for it. You can see where each tier lands on our VPS hosting page and start at whatever size fits, then resize later.
The self-hosted email server VPS checklist that actually matters
Software installs in an afternoon. The deliverability plumbing is where mail gets made or broken. Here is the order we walk people through:
- A sending IP with reverse DNS that matches. The receiving side does a PTR lookup on your sending IP. If it doesn't resolve — or resolves to some generic
vps-1234.provider.netstring — you're penalised before your message is even read. Whatever sends your mail needs a static IP whose PTR points at your mail hostname. We don't offer custom reverse DNS on NODED IPs, so on our VPS that means relaying outbound mail through a smarthost or transactional email provider that has it. - Matching forward and reverse DNS. Your A record (
mail.example.com → IP) and your PTR (IP → mail.example.com) must agree. This "FCrDNS" check is table stakes for the big mailbox providers. - SPF, DKIM, DMARC. Publish an SPF record for whatever sends your mail (your relay, if you use one), let your stack sign with DKIM, and add a DMARC policy. Mailcow and Mail-in-a-Box generate the DKIM keys for you; you just paste the TXT records.
- A relay for outbound mail. Hand outgoing mail to a smarthost or transactional provider over its authenticated submission port (587 or 465). It delivers from IPs with proper reverse DNS, which most receiving servers now expect.
- A clean starting IP. Check the IP's reputation against the common blocklists before you send a single message at volume. A history-free or clean address is the difference between a warm-up and a fight.
Deliverability is the real job
This is the part the tutorials skip. Getting mail accepted is easy; getting it into the inbox is a reputation game you play over weeks. New IPs have no sending history, so providers throttle you until you've proven you're not a spam cannon. Warm up gradually — real mail to real recipients, low volume first, rising as engagement builds. Keep your bounce rate low, honour unsubscribes, and never buy lists. Monitor your DMARC aggregate reports so you can see what's failing and where.
The one thing you cannot fix in software is the neighbourhood. On a large budget cloud, you're sharing a reputation pool with thousands of anonymous VMs, some of which are actively sending spam. When one of them gets a /24 listed, you inherit the blast radius. That's why the address space underneath your mail server matters as much as the config on top of it. We run our own network on AS60982, which means blocklist hygiene on our ranges is our problem to manage, not a faceless upstream's. We don't offer custom reverse DNS, though, so for outbound mail from a NODED VPS use a smarthost or transactional email provider whose sending IPs carry proper PTR, SPF and DKIM, and keep your own server for receiving, storage and webmail.
Why EU jurisdiction is a trust signal
Where your mail physically lives is a policy decision. NODED is operated by X ZONE IT SRL in Romania, inside the EU, which puts your correspondence under GDPR and European data-protection law rather than a jurisdiction where a subpoena travels further than you'd like. For private mail — legal, medical, journalistic, or simply personal — that jurisdiction is the whole point of self-hosting. If compliance is a formal requirement for you, we go deeper on it on our GDPR-compliant hosting page.
The honest maintenance note
We won't pretend this is set-and-forget. A self-hosted mail server is a service you now operate. That means OS and stack updates, certificate renewals (automated, but watch them), backups of your mail store, and the occasional evening spent decoding why one provider started greylisting you. Rspamd rules drift. Blocklists change. TLS requirements tighten. None of it is hard, but it is ongoing, and if nobody on your side owns it, entropy wins. Budget an hour a month on a good month, an evening on a bad one. If that sounds like a burden rather than a hobby, a managed inbox is the right call — and we'd rather you knew that now than after a weekend of chasing PTR records.
How Noded Can Help
We give you the layer under the mail server that you can't fix with config. Every VPS ships with a static IPv4 (plus free IPv6 in Romania, the Netherlands and Germany), root SSH, SSD storage, and unmetered traffic — enough to run Mailcow, plain Postfix, or Mail-in-a-Box without fighting the box. Because we run our own AS60982, we care about keeping our ranges off blocklists because it's our name on them, not a reseller's. We don't set custom reverse DNS, so pair the server with a smarthost or transactional provider for outbound mail. Deploys take about a minute, so you can spin up, test deliverability, and resize if you need more headroom. In any of our six EU countries, everything sits in the EU, run by an EU operator (X ZONE IT SRL in Romania), with 100 Gbps of DDoS protection included on every plan. Start on our email hosting VPS page and pick a tier.
FAQ
Can I set reverse DNS (PTR) on a NODED VPS?
No. We don't offer custom reverse DNS, either set by us or self-service, so the PTR on your VPS IP won't match your mail hostname. Matching forward and reverse DNS is a hard requirement for inbox delivery, so relay outbound mail through a smarthost or transactional email provider whose sending IPs have proper PTR, SPF and DKIM, and publish SPF and DKIM for it on your domain. Your own server still handles receiving, storage and webmail.
How much RAM does a self-hosted mail server need?
Mail-in-a-Box runs comfortably on a 2GB VPS for one or two domains. Mailcow's documented minimum is 6 GiB of RAM plus 1 GiB of swap in its default configuration (ClamAV and full-text search are the big consumers), so plan on an 8GB VPS. You can start small and resize as your volume grows — see the tiers on our VPS hosting page.
Will my mail actually reach the inbox?
That depends on reputation, not just setup. With correct SPF, DKIM, DMARC, matching FCrDNS, and a clean sending IP — on a NODED VPS, your relay's — you clear the technical bar. From there it's a warm-up: send real mail at rising volume, keep bounces low, and monitor your DMARC reports. Before you start, check both your relay's sending IPs and your NODED IP against the common blocklists, and open a ticket if the NODED IP is listed.
How should my mail server send outbound mail?
Since NODED IPs don't carry custom reverse DNS, the setup we recommend doesn't rely on it: your server hands outbound mail to a smarthost or transactional provider over its authenticated submission port (587 or 465), and that provider delivers it from IPs with proper PTR.
Why choose EU hosting for email?
Jurisdiction is a privacy decision. NODED is operated by X ZONE IT SRL in Romania, inside the EU, so your mail falls under GDPR and European data-protection law. For private or sensitive correspondence, that jurisdiction is often the entire reason to self-host in the first place.