Run your own mail server on a no-KYC VPS
Port 25 is open on every Blackbox, and you set the reverse DNS yourself in the panel. The disk can be encrypted with a passphrase only you hold, and the account is a generated 32-character credential with no name or email behind it.
- Port 25 open
- Reverse DNS in the panel
- IPv4 and a routed IPv6 /64
What a Blackbox gives a mail server
What the host already provides before you install a mail stack.
- Port 25
- Open on every Blackbox. The server can deliver directly to other mail servers, with no relay in between.
- 反向 DNS
- Set it yourself under Manage, rDNS, for the IPv4 and the IPv6 address. Our nameserver has the new PTR within a minute.
- Addresses
- One dedicated IPv4 address and a routed IPv6 /64, in IP space announced from AS395904.
- Your own prefix
- Bring an IPv4 or IPv6 prefix from the panel. We announce it from AS395904 once its ROA and route object check out.
- Encryption
- On Linux images, AMD SEV-SNP encrypts guest memory and optional LUKS2 disk encryption takes a passphrase you type over SSH at boot. No guest agent runs inside.
- 转移
- 2 to 32 TB per 31 days by plan, on a 10 Gbps port. Past the allowance the port drops to 10 Mbps until the period rolls over.
- Account and payment
- A generated 32-character credential, no email or ID. Pay in Bitcoin, Monero, Litecoin, Ethereum, USDT or USDC, received on nodes we run, by card through Stripe (which keeps its own record of the payment), or with cash by mail.
- Where
- Montreal and Amsterdam now. New York City on pre-order: paid now, deployed when the node lands.
What Gmail and Outlook check
Port 25 and the PTR get mail off the server. These decide whether it reaches the inbox.
Forward-confirmed reverse DNS
Google requires a PTR on the sending address that names a hostname, and an A or AAAA record on that hostname that points back to the same address. Use one hostname in the PTR, the HELO and the MX.
SPF or DKIM, and alignment
Gmail wants SPF (RFC 7208) or DKIM (RFC 6376 from September 2011, now Internet Standard STD 76) on every message. Above 5,000 messages a day it also wants DMARC, a From domain that aligns with them, and one-click unsubscribe on marketing mail.
TLS on the connection
Google lists TLS as a requirement for every sender. MTA-STS (RFC 8461) lets your domain tell other servers not to fall back to plaintext when they deliver to you.
A low spam rate
Google expects a spam rate under 0.3% in Postmaster Tools. Since May 2025 Microsoft applies a comparable list to senders of more than 5,000 messages a day into Outlook.com, Hotmail.com and Live.com.
A slow start on a new address
A new IP has no reputation yet. Spamhaus advises at most 1,000 emails a day from a new or dormant IP at first, and no doubling of daily volume in the first week. Its Policy Blocklist covers more than 1.4 billion IPv4 addresses.
Pre-flight: check the server can send mail
Run it as root on a fresh Debian 13 Blackbox, before you install a mail stack. 203.0.113.10 and example.net are placeholders.
# Sources for the requirements on this page:
# https://support.google.com/a/answer/81126 Gmail sender rules
# https://www.spamhaus.org/faqs/dnsbl-usage/ DNSBL queries
# https://www.spamhaus.org/blocklists/policy-blocklist/ PBL
# https://www.spamhaus.org/faqs/marketing-email/ new-IP warm-up
# https://datatracker.ietf.org/doc/rfc7208/ SPF
# https://datatracker.ietf.org/doc/rfc6376/ DKIM, STD 76
# https://datatracker.ietf.org/doc/rfc9989/ DMARC, May 2026
# https://datatracker.ietf.org/doc/rfc8461/ MTA-STS
apt update && apt install -y dnsutils netcat-openbsd openssl
# 1. The addresses this machine sends from: one IPv4 and a routed /64.
ip -4 addr show scope global | grep inet
ip -6 addr show scope global | grep inet6
# 2. Forward-confirmed reverse DNS. Set the PTR first (Manage, then
# rDNS), then check that both directions agree. Google: the PTR
# hostname "must also have an A (for IPv4) or AAAA (for IPv6)
# record that resolves to the same public IP address".
dig +short -x 203.0.113.10 # expect: mail.example.net.
dig +short A mail.example.net # expect: 203.0.113.10
# 3. Outbound tcp/25 is open on Blackbox. This confirms it.
nc -vz -w 5 gmail-smtp-in.l.google.com 25
# A 220 banner and a 250-STARTTLS line mean mail can leave this machine.
printf 'EHLO mail.example.net\r\nQUIT\r\n' \
| timeout 15 nc gmail-smtp-in.l.google.com 25 | head -20
# 4. TLS, which Google requires from every sender.
printf 'QUIT\r\n' | openssl s_client -quiet -crlf -starttls smtp \
-connect gmail-smtp-in.l.google.com:25 2>&1 | head -12
# 5. Is the address already listed? Ask from the server's own resolver:
# Spamhaus answers 127.255.255.254 to queries from public resolvers.
# Reverse the octets: 203.0.113.10 becomes 10.113.0.203
dig +short 10.113.0.203.zen.spamhaus.org
# An empty answer (NXDOMAIN) is what you want. 127.0.0.x means listed.
# 6. Once the stack is installed, check what is listening where.
ss -ltnp | grep -E ':(25|465|587|993)\b'Publish the DNS records in this order
example.net is the mail domain, mail.example.net the host and 203.0.113.10 its address.
PTR first
Open Manage, then the rDNS tab, and enter mail.example.net for the IPv4 address, and for the IPv6 address if the server will send over IPv6. Our nameserver has it within a minute; resolvers holding the old answer update when its TTL runs out.
A, AAAA and MX
Publish mail.example.net A 203.0.113.10. Add an AAAA only if the server really sends over IPv6. Then publish example.net MX 10 mail.example.net.
SPF and DKIM
Publish exactly one SPF record at the apex. v=spf1 mx -all allows the hosts in your MX and nothing else. Put the DKIM key at selector._domainkey.example.net and sign with the domain in From, or alignment fails.
DMARC, then MTA-STS
Start with _dmarc.example.net TXT v=DMARC1; p=none; rua=mailto:dmarc@example.net, read the aggregate reports, then move to quarantine and reject. RFC 9989 (May 2026) is the current DMARC spec and replaces RFC 7489. Last, publish _mta-sts.example.net TXT and serve the policy at https://mta-sts.example.net/.well-known/mta-sts.txt, as RFC 8461 requires.
Which mail stack fits which plan
Pick the stack before the plan. Their documented memory figures run from 512 MB to 6 GiB.
| What it is | Documented minimum | Blackbox plan | |
|---|---|---|---|
| Stalwart | An all-in-one Rust server for SMTP, IMAP, JMAP and POP3 | No stated minimum. Default limits come to about 2.4 GiB on a 2 GiB host, 1.4 GiB with no very large accounts | Core, 2 vCPU and 4 GB, $9.99 a month |
| mailcow: dockerized | Postfix, Dovecot, Rspamd and SOGo in containers | 6 GiB RAM plus 1 GiB swap, 20 GiB disk before mail | Plus, 4 vCPU and 8 GB, $19.99 a month |
| Mail-in-a-Box | A turnkey installer for one Ubuntu release | Ubuntu 22.04 x64 and 512 MB of RAM | Core, 2 vCPU and 4 GB, $9.99 a month, installed from your own ISO |
What each project documents
Stalwart's system requirements say memory use is set mainly by limits in the configuration, and note that "an idle server stays well below its limits and a busy one approaches them." Its memory sizing guide works through a 2 GiB host where the default limits total 2429 MiB, of which 1024 MiB are large-account caches that stay empty unless an account has a very large mailbox or calendar, leaving 1405 MiB. Blackbox Core (2 vCPU, 4 GB) has twice the memory of that example host.
mailcow's prerequisites page asks for "6 GiB + 1 GiB swap (default config)" and "20 GiB (without emails)" of disk. It runs on Debian 11 to 13, Ubuntu 22.04 or newer, Alma Linux 8 or 9 and Rocky Linux 9, and needs inbound TCP 25, 465, 587, 143, 993, 110, 995, 4190, 80 and 443. Blackbox Plus (4 vCPU, 8 GB) is the smallest plan that fits.
The Mail-in-a-Box setup guide says you "must choose the Ubuntu 22.04 x64 (server edition) operating system" on "a machine with at least 512 MB of RAM", and that you "must follow your cloud provider's instructions for setting the reverse DNS". On Blackbox that is the rDNS tab. Ubuntu 22.04 is not one of the Blackbox images, so you install it from your own ISO, which works on a Blackbox deployed without measured boot.
The sender rules quoted on this page come from Google's sender guidelines and Microsoft's post on Outlook's high-volume sender rules. Reverse DNS works the same way on Blackbox in Montreal and Amsterdam, and the SEV-SNP page covers what memory encryption protects and what it does not.
Where your mail sits
A mail server keeps your correspondence on its disk in plain text, and whatever it is processing sits in memory. On Blackbox the CPU encrypts that memory, and the disk can be encrypted with a passphrase only you hold.
- Optional full-disk encryption (LUKS2) on Linux images. You unlock it over SSH into the initramfs at boot, so losing the passphrase means losing the server.
- AMD SEV-SNP memory encryption on Linux images, and no guest agent, so the host has no channel to run commands inside.
- Measured boot you can check with blackbox-verify before you type the passphrase.
- It protects memory, CPU state and the disk. Mail in transit relies on TLS, and we can still power the server off.
Blackbox plans
Reverse DNS is set from the Blackbox panel, so these are the plans to run mail on.
| 套餐 | vCPU | 内存 | NVMe | Traffic | Where | 价格 |
|---|---|---|---|---|---|---|
| Blackbox Core | 2 | 4 GB | 50 GB | 4 TB per 31 days | 蒙特利尔阿姆斯特丹纽约市 (launch pre-order) | $9.99/mo |
| Blackbox Plus | 4 | 8 GB | 100 GB | 8 TB per 31 days | 蒙特利尔阿姆斯特丹纽约市 (launch pre-order) | $19.99/mo |
| Blackbox Max | 6 | 16 GB | 200 GB | 16 TB per 31 days | 蒙特利尔阿姆斯特丹纽约市 (launch pre-order) | $39.99/mo |
| Blackbox Ultra | 8 | 32 GB | 400 GB | 32 TB per 31 days | 蒙特利尔阿姆斯特丹纽约市 (launch pre-order) | $79.99/mo |
Deploy a mail server on Blackbox
Pay in Monero, Bitcoin, card or cash for any term from 7 to 365 days, then set the PTR yourself.
Questions
Is outbound port 25 open on Servury?
Yes. Port 25 is open on every Blackbox server, so your mail server can deliver straight to Gmail, Outlook and everyone else without a relay. Step 3 of the pre-flight script checks it from the machine. Blackbox is also where you set reverse DNS yourself, so it is the line to run mail on.
Can I set my own reverse DNS (PTR record)?
You can on any Blackbox server. Open it in Manage, go to the rDNS tab, and enter a hostname for the IPv4 address, the IPv6 address or both. Our nameserver serves the new PTR within a minute. The standard VPS and VDS line has no rDNS tab.
How much RAM does a self-hosted mail server need?
It depends on the stack. Stalwart's memory use is set mainly by its configuration limits, and its sizing guide works through a 2 GiB host where the default limits total about 2.4 GiB, or about 1.4 GiB when no account is unusually large, so Blackbox Core (2 vCPU, 4 GB, $9.99 a month) covers it with room to spare. mailcow asks for at least 6 GiB plus 1 GiB of swap, which means Blackbox Plus (4 vCPU, 8 GB, $19.99 a month).
Will Gmail accept mail from a brand new VPS address?
Yes, if the basics are in place: Google requires SPF or DKIM, matching forward and reverse DNS, a TLS connection and a spam rate below 0.3% in Postmaster Tools. Above 5,000 messages a day it also wants DMARC, an aligned From domain and one-click unsubscribe on marketing mail. Microsoft has applied a comparable list to senders of more than 5,000 messages a day into Outlook.com, Hotmail.com and Live.com since May 2025. Start a new address slowly: Spamhaus advises no more than 1,000 messages a day at first. A personal domain with a few accounts is realistic. A newsletter to 50,000 strangers from a new address takes months.
Does hosting mail on an anonymous VPS make the mail anonymous?
No. Signup asks for nothing, so we have no identity to hand over. A mail server still publishes a domain, an MX record, a hostname and a PTR, and every message you send lands in someone else's mailbox with its headers. A no-KYC host removes one link to you: the hosting account.
Can I bring my own IP space for sending?
On Blackbox, yes. Add an IPv4 or IPv6 prefix in the panel, create the ROA and IRR route object it asks for, and we announce it from AS395904 once both check out. Reputation belongs to the address space, so the prefix brings its sending history with it, good or bad.
What is not allowed on a mail server here?
Spam and unsolicited bulk mail, fraud and phishing are prohibited by the terms of service, and so is cryptocurrency mining on any server. Running your own mail server is ordinary use.
Guides on this topic
- How to Set Up a Self-Hosted VPN with WireGuard on a VPSTen minutes from a fresh Ubuntu server to a WireGuard VPN you control: keys, config, forwarding, firewall, a phone client by QR code, and the two settings that...
- Self-Hosted Apps vs SaaS: Why Running Your Own Nextcloud, Vaultwarden, or Pi-hole Beats Trusting a Third PartyWhat changes when you run your own Nextcloud, Vaultwarden, or Pi-hole instead of trusting a SaaS provider, and how an anonymous VPS narrows the last privacy...
- Why Developers Are Self-Hosting AI Agents and LLMs Instead of Relying on Cloud AI PlatformsWhy developers are moving language models and agents onto their own VPS, keeping prompts, documents, and agent memory private instead of sending them to a...
- VPS vs VPN: Why a VPN Alone Isn't Enough for Real Privacy & OpsecA VPN moves your trust from your ISP to one company that sees all your traffic and whose no-logs promise you can't verify. Why real privacy needs a VPS you...