Several of my self hosted services need to be able to send minor occasional emails for things like changing passwords or other notifications.
I’ve never been interested in the hassle of self-hosting my personal email, since I’ve heard about it being difficult. But for my little local services to have one admin@ or noreply@ to send from, with just a small handful of friends and family as users, maybe it’s simpler than a full personal email replacement would be? I’m not too concerned, for example, if they have to check their spam folders. As long as the email still lands. And probably wouldn’t need to worry about incoming emails.
What are you using for this type of thing? Hoping to have something not too complicated, and FOSS.
Edit: I also would like it to come from ____@mydomain.com


@crandall selfhosting an email server is far from being a hassle. Nowadays it is really easy. You can setup everything in less an hour.
I use stalwart + a postfix relay on a cheap vps.
Ah yes. Fuck with dns, reverse dns/ptr records, dmarc, dkim, spf, verify server is not on a blacklisted ip in spamhaus, stand up a server, then implement anti spam filters, and hope anything you send doesn’t end up in someone else’s spam filters, as well as monthly checks to make sure no spam lists have sudddenly added your domain/ip to said lists.
But hey easy right?
Actually yes, if you take each piece one step at a time it’s not that bad, as long as you are not expecting a fully functioning mail server on day 1 it’s relatively easy.
Yeah, this is self hosting after all. If you don’t expect some challenges to work though then you’re not gonna not have a good time.
The crazy thing is I can do a mail server easily, but I always get stuck or annoyed with docker, everyone says docker is easy 🤷
Yeah that’s going to depend a lot on the images you’re running. If it’s a published one the likely it’ll have a compose or at least a one liner to get it running. But yeah there can always be issues with hard coded IDs and if you want to give the host folders 777 or limit them. Are you running selinux and that’s going to get in the way. Did they not mention capabilities that needed to be added?
And if you’re building your own or extending that a whole other ball of wax.
And I typically run on k8s so that adds a whole other layer of complexity. But I’ve been using it for years and I’m actually more comfortable with it than just docker or podman.
It is kind of a hassle to get all your DNS set up so your mail doesn’t go to spam. If you don’t already know what you’re doing it will probably take over an hour.
Even if properly setup it could still go to spam until you get your reputation score up which with low volumes will take ages.
So i was thinking about this from a dns perspetive. If you have a dns forwarder can you not configure it to ensure that emails from the local smtp server never leave tour lan?
If you have local SMTP and IMAP you can send mail on your own systems, or if you’re not using containers and you run everything on the same system you may even be able to skip SMTP and just deliver directly. But if you want to receive mail from outside your LAN you’ll need a way to access your IMAP server.