Run a mail server on a VPS with a clean IP

The economics of high-volume cheap hosting work against mail. Large providers cycle IPv4 addresses through thousands of short-lived customers, and a meaningful share of those customers send spam, run compromised software, or get terminated for abuse. By the time an address is recycled to you, it may already sit on Spamhaus, Barracuda, SORBS, or a dozen DNSBLs you have never heard of. Some ranges are flagged wholesale because a neighbouring address in the same /24 misbehaved.

The result is a familiar frustration: a brand-new mailbox that bounces or gets spam-foldered on its first send, with no abuse of your own to explain it. You inherited the reputation of whoever held the address before you. No amount of correct SPF or DKIM configuration fully undoes a poisoned IP; you are repairing damage someone else caused instead of building reputation from a clean slate.

The fix is not magic, it is sourcing discipline. We screen IP allocations before they reach customers and avoid the rapid-recycle churn that poisons budget ranges. Each VPS ships with a dedicated clean IPv4 and an IPv6 /64, not a shared sending pool where another tenant can torch the reputation you depend on.

You do not have to take that on faith. Before you buy, look up our ranges on Spamhaus, AbuseIPDB and Cisco Talos, and check them against the major DNSBLs. After deploy, if you ever land on an address that is already flagged, request a swap through the panel. This clean-IP posture is part of our wider offshore VPS footprint, where each of the eight locations carries its own screened space rather than a single recycled block.

A mail server is not a heavy workload for a personal or small-domain setup. The Cub tier (1 vCPU, 2 GB RAM, 40 GB NVMe) comfortably runs Postfix, Dovecot and a spam filter for a single domain with a handful of mailboxes. Step up to Scout (2 vCPU, 4 GB, 70 GB NVMe) if you want headroom for Rspamd, ClamAV, a webmail front end, and several domains under one server.

RAM is the constraint that matters most, because antivirus and Bayesian spam scanning are memory-hungry. Disk fills over time as mailboxes grow, so size storage for retention rather than for today. Every tier includes unlimited traffic, so high inbound volume or large attachments will not meter you, and the all-NVMe storage keeps mailbox indexing and search responsive as the maildir grows.

Receiving mail servers judge you on four signals. Get all four right or expect rejections regardless of how clean the IP is:

• PTR / reverse DNS — the IP must resolve back to a hostname that matches your sending domain. A missing or generic PTR is one of the fastest routes to an outright rejection.
• SPF — a TXT record on your domain that authorises your VPS IP to send for it, for example v=spf1 ip4:YOUR_IP -all.
• DKIM — cryptographic signing so receivers can verify the message was not altered and genuinely came from your domain. Publish the public key as a TXT record at the selector you configure in your MTA.
• DMARC — a policy record that tells receivers what to do when SPF or DKIM fail, and where to send aggregate reports so you can see how your mail is being treated.

On the software side, Postfix for sending and Dovecot for IMAP/POP is the canonical stack; pre-built distributions like Mailcow or Mail-in-a-Box bundle everything if you would rather not assemble it by hand. Deploy guidance and the panel walkthrough live in the docs.

Reverse DNS is the one record you cannot set yourself, because the PTR lives in the in-addr.arpa zone owned by whoever controls the IP allocation, not in your domain's zone. You request it from us, through the control panel, for both your IPv4 address and any IPv6 address you send from.

Set the PTR to the exact hostname your mail server announces in its SMTP HELO/EHLO, and make sure that hostname resolves forward to the same IP. This forward-confirmed reverse DNS (FCrDNS) match is checked by nearly every major receiver. As with all support here, you handle this through the panel rather than email, which is deliberate while you are still bringing your own mail server online.

A clean IP is a starting position, not a guarantee you cannot lose. The fastest way to undo it is to behave like a spammer on day one. Three rules keep you off the lists:

• Warm up gradually. Do not blast a large list from a cold IP. Start with low volume to engaged recipients and ramp over days and weeks so receivers learn your sending pattern as legitimate.
• Rate-limit outbound. Cap messages per hour and per recipient domain. Sudden spikes look like a compromised host and trigger automated throttling or listing.
• Never run an open relay. Lock Postfix to authenticated senders only and require TLS for submission. An open relay is found and abused by bots within hours, and the resulting listing is hard to reverse.

Keep your software patched, monitor logs for unexpected outbound volume, and remove any compromised account immediately. Most listings come from a hijacked mailbox or a misconfigured relay, not from the host.

Reputation is ongoing maintenance, not a one-time setup. Make a habit of running your sending IP and domain through MXToolbox and the Spamhaus lookup, which together cover the DNSBLs that matter most. Enrol in Google Postmaster Tools and read your DMARC aggregate reports to catch problems before they become widespread rejections.

If you ever find yourself listed, identify the cause first, fix it, then use the listing provider's delisting form. Removing the symptom without fixing the source just gets you relisted. For a step-by-step walkthrough of the lookup tools and what each result means, see our guide on how to check if an IP is blacklisted. The same no-KYC signup and crypto payment that get you online apply whether you are running one mailbox or several domains.

No host can guarantee permanent inbox placement, and any provider that promises it is selling you something it cannot deliver. Deliverability is a shared responsibility: we supply clean, screened IP space and the PTR control you need, but inbox placement also depends on your content, your sending behaviour, recipient engagement, and the constantly shifting heuristics of the big mailbox providers.

What we can honestly offer is a fair starting line, an IP without someone else's baggage, full control of the records that matter, unlimited traffic so volume never meters you, and a swap through the panel if an address is ever flagged. From there, disciplined warm-up and correct authentication do the rest. You pay with crypto, including Monero, with no ID, and deploy in about sixty seconds once payment confirms.