Use case · Mail

Mail server hosting. Your correspondence, your box.

Self-hosted mail is the last honest inbox: no provider scanning your threads for ad keywords, no account tied to a phone number, no third party holding the keys. On VPSRento the box is yours down to the disk encryption — and the no-KYC account fits mail the way mail deserves.

  • rDNS supported
  • Clean IPs — 40+ DNSBL checks
  • Port 25 opens after 30 days
  • No KYC · crypto-only
deploy — mailcow, bucharest
Why this use case

The inbox nobody else reads

Free mail is not free; you pay with the contents of your inbox. Self-hosting ends that trade: the mail store sits on hardware you root, the transport is encrypted in transit, and the jurisdiction holding the disks is one you chose. For journalists, lawyers, therapists — or anyone whose correspondence is genuinely theirs — that is the point.

VPSRento fits the use case in two structural ways. First, no KYC: the account is a 24-character token, payment is crypto-only, so the identity layer of your mail infrastructure is empty by construction. Second, clean IPs: every address is checked against 40+ DNSBLs before it is assigned to you, which matters enormously when your deliverability starts on that IP's reputation.

The honest part: self-hosted mail is a craft. You will run SPF, DKIM, DMARC, TLS and backups yourself. We give you the clean, stable foundation — rDNS, clean IP, uptime — and we are straight with you about the port-25 policy before you pay a satoshi.

What the box comes with

  • Full root, any stack. mailcow, Stalwart, or bare Postfix + Dovecot — your call, no panel forced on you.
  • rDNS on request. Your server announces mail.your-domain.tld — the first thing receiving servers check.
  • Clean IP start. 40+ blacklist checks before assignment; flagged IPs are quarantined, never sold.
  • Submission ports open day one. 587 and 465 work immediately for your own clients.
  • Disk encryption on all nodes and no activity logs — the host layer stays as quiet as your inbox should.
Setup pointers

From root shell to first message in an evening

The short version — a hardened KVM box, a mail stack you actually own, and the DNS records that make you look legitimate.

# Debian 13 — mailcow (dockerized) $ apt install docker.io git $ git clone https://github.com/mailcow/mailcow-dockerized $ cd mailcow-dockerized && ./generate_config.sh

Checklist

  • Harden first: the VPS hardening checklist — SSH keys, firewall, fail2ban — takes twenty minutes. Do it before anything listens.
  • Set rDNS to match your mail hostname via the client area, then keep HELO, PTR and TLS certificate aligned.
  • Publish SPF, DKIM and DMARC before sending anything — receiving servers treat missing records as a confession.
  • Wait out the 30 days, then open a ticket to unfilter port 25. Use the time to warm up with submission ports and test mail.
  • Snapshot your mail store. Daily offsite snapshots are a $1.99/mo add-on — cheap against a lost mailbox.

The port-25 policy, verbatim

  • Filtered by default. Outbound port 25 is blocked on every new server.
  • Opened on request after 30 days, for a properly configured server with matching rDNS. One ticket, answered by a human.
  • Submission is open now. Ports 587 and 465 are never filtered — your own clients work from minute one.

Why the friction? Because spam is the single most damaging abuse vector in hosting, and hosts that open port 25 instantly become disposable spam cannons — which poisons the IP reputation of every honest customer sharing the neighbourhood. The 30-day window filters the throwaway crowd; the rDNS requirement filters the careless. Both filters protect your deliverability more than they cost you.

Honest note: if your plan is bulk or marketing mail, this is not your host. Bulk sending violates the AUP regardless of port state. Personal and organisational correspondence is what this page is for.
Recommended setup

SV-Nano for a personal domain, SV-Core for an organisation

Mail is light on CPU and honest about storage — size the NVMe to your mailbox habits and the RAM to your spam filter's appetite.

Mail profile Plan NVMe Romania Netherlands
Personal domain (1–5 users)SV-Nano · 1 vCPU · 2 GB25 GB$5.99$5.99
Family / small orgSV-Core · 2 vCPU · 4 GB60 GB$10.99$10.99
Mailbox-heavy / mailing listsSV-Pro · 4 vCPU · 8 GB120 GB$19.99$19.99

Full specs on the Linux VPS page; live per-location prices on the Bucharest and Amsterdam location pages. Quarterly −10% · 6 months −30% · annual −50% — best value (e.g. SV-Nano: $5.99/mo → $3.00/mo equivalent billed annually).

FAQ

Mail server hosting, answered

It is filtered by default, not blocked forever. As an anti-spam measure, port 25 opens on request once the server has been running for 30 days with a properly configured mail server and matching reverse DNS. Submission ports 587 and 465 are open from day one, so your own mail clients work immediately. The policy is written into the AUP — no surprises.

Deliverability is work, and no honest host promises otherwise. What we provide is a clean starting point: every IP is checked against 40+ DNSBLs before assignment, and rDNS is supported so your server announces a hostname matching your mail domain. From there, SPF, DKIM and DMARC records and gradual warm-up decide your reputation — that part is yours.

For a personal domain or a small family, SV-Nano at $5.99/mo covers it; a small organisation belongs on SV-Core at $10.99/mo for the extra RAM and 60 GB NVMe. For the stack, mailcow on Docker is the pragmatic route, while Postfix plus Dovecot suits minimalists. Harden the box with the VPS hardening checklist before anything touches port 25.

Your inbox, on your metal, in 55 seconds.

Pay with crypto, get root, and a mail server that answers to nobody's content policy but the jurisdiction you chose.