Why your own email server
- No price per contact. You pay for the server. The list can grow without the bill growing with it.
- Your data stays yours. The list, the logs and every bounce are on your own server.
- As many domains as you need. Many mail servers and domains from one panel.
- Every message is logged. Delivered, opened, bounced: you see all of it.
- Plug it into anything. Your website, CRM or booking system, over plain SMTP or an HTTP API.
What Postal is
Postal is an open source mail delivery platform for sending and receiving email from websites and apps. It runs in Docker on a Linux server. I run it on my own VPS next to other projects, and Claude Code set it up without touching any of them.
The hard part is deliverability
Sending is the easy part. Arriving in the inbox is the work: DNS records for SPF, DKIM and the return path, a reverse DNS name for the server's IP address, and a new IP that has to be warmed up slowly. Google's sender guidelines require every sender to have valid forward and reverse DNS and SPF or DKIM.
That is where Claude did the heavy lifting on my server: TLS, the DKIM key and a dedicated IPv4 pool. And it wrote down exactly which steps are still left.
Honest status. My Postal server runs, the admin panel answers over TLS, it has its own IPv4 pool and a DKIM key. The DNS records for sending through it are not published yet, so my business email still goes through Google Workspace. This guide shows the setup and the steps that remain. It does not show delivery numbers, because I do not have them yet.
One rule: only email people who asked
In Norway, marketing email to private persons needs their consent in advance (section 15 of the Marketing Control Act). Your own server changes what you pay, not who you may write to.