Zum Inhalt der Seite gehen
i think it's time to dispel the myth that #selfhosting #email is hard if a dumdum like me can set up https://github.com/docker-mailserver/docker-mailserver in a USD12/mo linode box (which also hosts my websites, so that's not USD12 for mail alone) in like 15 minutes

the hardest part is just getting the DNS DKIM, DMARC and SPF values right
mail-tester.com result of 10/10 indicating my self-hosted email server can send email and it won't be rejected or flagged as spam by most sensible email inboxes

GitHub - docker-mailserver/docker-mailserver: Production-ready fullstack but simple mail server (SMTP, IMAP, LDAP, Antispam, Antivirus, etc.) running inside a container.

Production-ready fullstack but simple mail server (SMTP, IMAP, LDAP, Antispam, Antivirus, etc.) running inside a container. - docker-mailserver/docker-mailserver
GitHub
#selfhosting #email
64 ΩMB
Getting things up and running is easy, sure, but what's the long term maintenance plan?

What happens if your IP gets listed on one of the block lists that makes it a pain to delist or outright extorts to delist? What about security considerations?

Every time someone dispels this myth they do it by showing how simple it is to get going, but they don't have details on the long term care and feeding requirements.

I'd love an update on how this is going in 6-12 months!
Gosplan Cosplay :jorts:
DKIM goes a long way in staying off the block lists. I know because I have the same setup @ Linode, for a couple years, with no issues.

I would add some key steps:
- rDNS
- TLS
- reject bad DKIM when receiving
- check at least one DNSBL when receiving
- IPv6 because it's 2025

Configuring email is a journey :) But definitely learnable.
64 ΩMB
Great additions! I'm all for people self hosting as much as they can, provided they understand what they're doing. Following a guide step by step without fully grasping the tech sets them up for a bad time at some point down the road.
⇧