Every time we get paged about "our emails are going to spam," the root cause is almost always the same: the sending IP has a reputation problem, and nobody owns that IP but a shared pool of strangers. If you're running your own mail server — Postfix, Exim, whatever — a dedicated IP address for mail server hosting is the difference between deliverability you control and deliverability you inherit from someone else's spam run. This is the notebook we hand anyone standing up a new mail server: the warm-up schedule, the PTR walkthrough, and the parts of the stack that fail silently if you skip them.
Why Shared IPs Sink Deliverability
On a shared IP, your reputation is the average of everyone sending from that address. One tenant blasting a purchased list can get the whole range greylisted or blocklisted by Spamhaus, Barracuda, or a receiving provider's internal filter — and you find out only when invoices and password resets stop arriving. There's no dashboard for "someone else on this IP just did something dumb," you just watch your bounce rate climb. A dedicated IP removes that variable: your sending history is your own, good or bad, and it's the only signal ISPs use to build a reputation score specific to you.
Dedicated IP vs Shared IP for Email Sending
The choice between a dedicated IP and a shared IP for email sending comes down to volume and control, not just cost:
- Shared IP — fine for very low, infrequent volume where you have zero control over co-tenants. Reputation is pooled; a neighbor's mistake is your outage.
- Dedicated IP — needed once you're sending transactional mail (invoices, tickets, password resets) at real volume, or self-hosting with full control over PTR, SPF, and rate limits. Reputation is entirely yours to build and protect.
If you're already running a VPS for your mail server, you already have the IPv4 address to dedicate — treat it like an asset, not an afterthought.
The IP Warm-Up Schedule
A brand-new IP with zero sending history looks like a compromised host to receiving servers. Ramp volume gradually so mailbox providers can build a profile before you hit real send volume. This is a widely-used ramp — adjust downward at the first sign of a bounce or complaint spike, and watch your own postmaster tools (Gmail Postmaster, Microsoft SNDS) at every step:
| Day | Max emails/day (approx.) | Notes |
|---|---|---|
| 1–3 | 50 | Your most engaged contacts only — people who open and reply. |
| 4–7 | 100–200 | Double every 2 days if bounce rate stays under 2% with no spam complaints. |
| 8–14 | 500–1,000 | Mix in regular transactional traffic, not just high-engagement contacts. |
| 15–21 | 2,000–5,000 | Keep doubling every few days, monitoring complaint rate. |
| 22–30 | Full volume | Only once bounce/complaint metrics are stable at the prior step. |
The rule underneath the table: never double volume and change something else — a new template, a new sending domain, a burst of unengaged recipients — on the same day. Isolate variables so a reputation dip has one obvious cause.
Reverse DNS and PTR Records: The Walkthrough ISPs Actually Check
Forward DNS says "mail.example.com points to this IP." Reverse DNS (a PTR record) says "this IP belongs to mail.example.com" — and most receiving mail servers reject or heavily penalize mail from an IP with no PTR record, or one that doesn't match the sending domain. This is the single most common misconfiguration we see on self-managed mail servers:
- Confirm you have a dedicated, static IP — you can't set a meaningful PTR on an address that changes or that you share with other tenants.
- Set your HELO/EHLO hostname. In Postfix, that's
smtp_helo_nameinmain.cf, and it should match the hostname you're about to point the PTR at (e.g.mail.yourdomain.com). - Request the PTR record from whoever controls the IP block — the reverse zone belongs to the network the IP lives on, so this is a support request to your host, not a change in your registrar panel.
- Verify it resolves both ways. A forward lookup of your hostname should return the IP, and a reverse lookup of the IP should return that same hostname — a mismatch in either direction triggers spam filters.
Because reverse DNS has to be set at the network level, check this before you sign up anywhere: can the provider actually set a custom PTR on your IP, and how fast do they turn it around? To be straight about our side: we don't offer custom PTR records on NODED IPs, so if your mail server runs with us, send outbound mail through a smarthost or transactional email provider whose IPs already carry proper PTR, SPF and DKIM.
Choosing a Dedicated IP Address for Mail Server Hosting in Europe
The checklist is short but each item matters: the IP needs to be dedicated, static (no change on reboot or migration), clean at signup (not recycled from a previous tenant's spam history), and paired with a host that will actually set a custom PTR for you.
Every Noded VPS ships with a dedicated IPv4 (plus free IPv6 in Romania, the Netherlands and Germany) and full root SSH, so you're not fighting a control panel to configure Postfix or Exim. Plans run from EUR4/mo (2GB RAM / 1 vCPU / 20GB SSD) up to EUR58/mo (32GB / 8 vCPU / 120GB SSD), all with unmetered traffic on a port shaped from 100 to 300 Mbps by plan, so outbound throughput isn't the bottleneck during a warm-up ramp. IP space sits on our own AS60982 with RPKI/ROA handled, which matters because filters increasingly weight whether an IP's routing origin is properly attested. Running a mail cluster large enough to need its own block? Our dedicated servers come with a /31 (one usable IPv4) included and /29–/27 subnets as add-ons, and BGP/BYOIP is available on request — see BYOIP for the minimums.
SPF, DKIM, and DMARC: The Non-Negotiables Alongside Your IP
A clean dedicated IP with a correct PTR gets you past the first filter, but it won't save you if SPF, DKIM, and DMARC aren't configured — modern filters treat "authenticated" and "reputable" as separate checks. SPF publishes which IPs may send for your domain; DKIM signs outgoing mail so receivers can verify it wasn't altered; DMARC tells receivers what to do when either check fails and hands you reports so you can catch abuse early. Set all three alongside your PTR record — doing them piecemeal just invites more rounds of "why is this still landing in spam."
How Noded Can Help
We run our own network, but we don't offer custom PTR records, so a NODED VPS is the home for the mail server itself — receiving, storage and webmail — while outbound mail goes through a smarthost or transactional provider with proper PTR, SPF and DKIM. Every VPS comes with a dedicated IPv4 address from day one (plus free IPv6 in Romania, the Netherlands and Germany), clean at signup, no recycled reputation baggage to inherit. If you're planning a self-hosted mail server and want to talk through your warm-up plan or whether you need BGP/BYOIP, reach out before you provision — easier to set up right than to fix after a blocklist hit. Start with a plan on our VPS hosting page.
FAQ
Do I need a dedicated IP address to run my own mail server?
Not strictly for a handful of test emails, but for any real transactional or marketing volume, yes. A shared IP ties your deliverability to every other tenant on that address, and you have no visibility or control over what they do.
How long does IP warm-up take before I can send full volume?
Roughly two to four weeks for most senders, ramping volume gradually while watching bounce and complaint rates. Sending everything at once on day one is the most common reason a new IP gets blocklisted immediately.
What's the difference between SPF, DKIM, DMARC, and a PTR record?
PTR (reverse DNS) proves your IP maps back to your hostname. SPF lists which IPs may send for your domain. DKIM cryptographically signs your messages. DMARC tells receivers what to do if SPF or DKIM fails. All four work together; missing one leaves filters a reason to flag you.
Can I get a custom PTR record set on my VPS's IP?
Not on Noded. A PTR can only be set by whoever controls the IP block, and we don't offer custom reverse DNS on our IPs. If you run the mail server with us, 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.
Is a dedicated IP better than an ESP (email service provider) for a self-hosted setup?
They solve different problems. An ESP manages IP reputation for you across pools it controls. Self-hosting on a dedicated IP gives you full control over your own server and reputation, at the cost of doing the warm-up and DNS configuration yourself — worth it if you want full ownership of your mail stack.