Bottom Line: Self-Hosting Email Is Possible, but “Free firstname@domain.com” Is Mostly a Deliverability Problem
The mail-server software can be free. Reliable delivery is not. You still need a domain, a stable public IP, working inbound/outbound SMTP, reverse DNS, TLS, reputation, spam filtering, backups and ongoing security maintenance. For most home users, a hosted mailbox on their own domain is cheaper in time and much easier to deliver reliably.
What You Need Before Hosting Mail at Home
- A domain you control.
- A public IP that is not behind CGNAT.
- Outbound TCP 25 that your ISP does not block.
- PTR/reverse DNS you can configure through the ISP or hosting provider.
- MX, SPF, DKIM and DMARC records.
- TLS certificates and continuous patching.
- Spam/abuse monitoring and tested backups.
PTR and DNS Reputation Are the Hard Parts on Residential Internet
Gmail's current sender requirements expect valid forward and reverse DNS plus authentication. The Gmail sender requirements is a practical deliverability benchmark. A home IP with no configurable PTR or poor reputation can cause mail to be rejected even when the SMTP server itself works.
SPF, DKIM and DMARC Are Not Optional Hygiene
SPF states which servers may send for the domain. DKIM signs messages cryptographically. DMARC ties authentication to the visible From domain and tells receivers how to handle failures. DMARC is standardized in DMARC policy.
If You Still Want to Self-Host, Isolate the Mail Server
Do not install a full mail stack directly into the ZimaOS base system. Run a dedicated Linux VM or a carefully maintained container stack with its own persistent storage, firewall and backup plan. The ZimaOS VM requirements provides the safer ZimaOS architecture.
Hosted Mail Is Usually Better for Personal Domains
If the goal is simply firstname@wardek.com, a low-cost hosted mailbox avoids IP reputation, PTR and port-25 constraints while still letting you own the domain. Self-host only if operating mail infrastructure is itself part of the project.
Do Not Expose an Unpatched Mail Server as a Learning Experiment
SMTP servers are continuously scanned and attacked. Test in a lab, learn the DNS/authentication model, then decide whether you are willing to maintain it 24/7. The ZimaBoard 2 server gives the hardware context, while the ZimaOS backup covers recovery.
Inbound Mail Has Its Own DNS and Availability Requirements
Receiving mail requires an MX record pointing at a hostname that resolves to your server, plus inbound TCP 25 reachability. If the server is offline for hours, sending servers may retry, but you should not treat retries as a backup strategy. A secondary MX is only useful if it is a real mail server that can queue and relay messages correctly.
Back Up Mailboxes and the Keys That Make the Server Work
A mailbox backup alone may not be enough. Preserve mail data, configuration, DKIM private keys, spam-filter state and any database used by the mail stack. Test restoring a mailbox and verify that a rebuilt server can still sign outgoing mail correctly. If you lose keys or rebuild DNS inconsistently, the new server may technically run while deliverability degrades.
FAQ
Can I host email for free at home?
The software can be free, but you still need a domain and usually pay indirectly for a suitable public IP, electricity, backups and your time.
Why do self-hosted emails go to spam?
Missing PTR, weak IP reputation, missing SPF/DKIM/DMARC, bad HELO identity or a residential IP range can all hurt delivery.
Do I need a static IP?
A stable public IP is strongly preferred. Dynamic addressing makes MX/PTR consistency and reputation much harder.
Can Cloudflare Tunnel solve SMTP hosting?
No. Standard internet email delivery depends on SMTP and DNS behavior that is different from publishing an HTTP web app through a tunnel.
Should I use Docker or a VM?
For a full mail stack, a dedicated VM provides a clearer operating-system, firewall and update boundary. Containers can work if you already understand the mail stack.
