A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
You should definitely set up a DMARC record to prevent other people from using your email domain to send spam. If you don't have DMARC configured, other email servers will give any senders the benefit of the doubt and accept mail that claims to be from your domain.
You can just set the DMARC record to reject 100% of unverified mail and call it a day. Since you aren't sending anything it won't affect you.
I would also set up SPF to disallow all IPs to send mail for that domain in case some system supports SPF but not DMARC.
Thanks to both of you.
I had the hope that DMARC, SPF and DKIM was stuff I could just ignore if not sending email. It seems I was wrong about that.
Those three are really not all that complicated, basically (apart from DKIM which you can ignore when not sending) they are just a couple of TXT DNS records you need to set once for your domain. Even if you were using DKIM it is just a keypair you generate and then put the public key into a DNS TXT record and configure your mail server to use the private key.
Just to flesh that out a bit... All you need is to add a TXT record to your DNS records:
Name: _dmarc.yourdomain.com
Value: v=DMARC1; p=reject; pct=100
will give any senders the benefit of the doubt and accept mail that claims to be from your domain.
You misspelled "black-hole your domain forever".
Some strict mail servers even blacklist you if the DMARC record is missing.
Some servers blacklist you even if you have DMARC, SPF, DKIM, DNS setup perfectly, but your IP is in a block of addresses that may or may not have been hosted by the same ISP of some unrelated server that was possibly compromised 10 years before you even set up the mail server. Ask me how I know.
Some servers blacklist you no matter what you do because you’re not a big player in the e-mail space… Outlook. Fuck Outlook. M365 doesn’t do that though.
Also the idea that reverse IPs are needed (in practice) when SPF, DKIM and DMARC are in use is insane. I have literally told you my public key and signed the e-mail. It’s me. You don’t need to check the damn PTR!
Is there any other beginner-friendly email service I should read about?
If you don't want to setup everything as you should there's also https://mailinabox.email/ and https://docs.mailcow.email/
Wow! this is exactly what I needed. Although, I didn't exactly ask for it.
Thank you very much
You’re welcome.
Should I setup DKIM, DMARC, SPF and reverse IP lookup?
This is no brainer to setup using mailcow. Just need to copy paste the provided TXT values from mailcow ui into your dns entries.
Mailcow is fantastic and very easy to deploy. I highly recommend it.
If your domain will NEVER send e-mail out, you only really need and SPF record to tell other servers to drop e-mail FROM your domain. Even that’s somewhat optional. If you ever plan on sending ANY outbound (you should at very least for the occasional ticket) then do DKIM, DMARC and SPF. The more of these you do, the less likely e-mails FROM your domain are to be flagged as spam.