posted in Selfhosted

Email for self hosted services? (Not personal email)

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

Edited ⁨⁨Sep⁩ ⁨17⁩, ⁨2026⁩, ⁨19:14⁩⁩enPage

Replying to @⁨crandall@lemmy.today⁩

My ISP offers unauthenticated SMTP for their customer addresses. It’s pretty heavily rate limited, but well enough for the occasional status email my system throws out. At least around here they are pretty common for residential customers, so that might be an option.

Other possibility is to set up SMTP relay to your network and give it credentials to an actual email account (with SMTP support, which isn’t granted these days). It can take in emails from your network without credentials and throw them to the internet with your account. It’s pretty simple to set up, search for postfix + smarthost. Added bonus is that you can read the replies to that address too via your email provider services.

Replying to @⁨crandall@lemmy.today⁩

I’m not too concerned, for example, if they have to check their spam folders. As long as the email still lands.

In that case, it really isn’t that much of a hassle. A basic mail system isn’t that complicated to set up (just make sure you have proper authentication and such, don’t host an open relay!). I actually did this not too long ago, using maddy, which unlike the traditional postfix+dovecot setup (which I had also been looking into) means you don’t even have to host separate services for SMTP and IMAP, and it also automates most additional things that are necessary nowadays for you, like TLS, DKIM, DMARC, and so on. Not quite everything though, there’s still stuff needed to do manually, mostly to set the SPF and DMARC records in the DNS, but it’s been working really well so far.

And really, the only mail provider you have to worry about for putting your mails into spam is gmail. They’re the worst. (maybe microsoft-hosted outlook too, but I haven’t encountered anyone using that)

maddy.emailHome - maddy

Replying to an earlier post

To be honest I haven’t done that deep search into how common it is for VPS providers to block port 25, but in the cases it has been relevant for me it has required at least raising a request and for instance for Hetzner being a customer for at least one month. I’ve figured that it’s a good thing and if a VPS provider has no restrictions at all their IP ranges are much more likely to have bad reputation and blocklist issues.

Replying to @⁨Theoriginalthon@lemmy.world⁩

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.

Replying to @⁨crandall@lemmy.today⁩

Maybe it’s a bit off-topic, but for my transactional emails, I use Scaleway TEM’s free tier. 300 mails/month are included, if you go above, it’s 0.25€ per 1000 mails. Dirt cheap. Never have I gone above the free tier limit. And it saves me from the hassle to have to setup something to send emails on thr server itself. Note that I had strange behavior while I tried to validate my domain while I used CloudFlare’s nameservers.

Replying to @⁨crandall@lemmy.today⁩

If its internal network traffic only, you can just use stalwart and add the DNS records to your network so that stuff can use SMTP.

Otherwise, (also with stalwart or your preferred software), you will want to use an SMTP relay so that outgoing messages will be delivered without the hassle of getting your domain reputational enough for sent messages not getting junked by the big email providers.

I’m extra lazy and haven’t set this up, so I just have a public mail server that only receives messages because my outgoing SMTP port is blocked by my ISP.

Replying to @⁨crandall@lemmy.today⁩

I’m hosting Mailcow in a cheap VPS, for both personal/family and system emails. Not something I’d necessarily recommend (it’s overkill for your requirements anyway), but the initial setup and maintenance are not nearly as difficult as people will try to make you believe. Before that I just used Gmail. You can point your sending application to smtp.gmail.com, STARTLS on port 587 or SSL on port 465, username is your email address, and a Gmail app password you create beforehand.

Replying to @⁨crandall@lemmy.today⁩

For inbound, I use Postfix + rspamd + dovecot directly to my server. Outbound, I used to send it directly from my server. I did this 15+ years with DKIM, DMARC, and SPF. It worked well for like 95% of the emails I sent, but I started relaying through smtp2go.com after I had just a couple really important emails not get delivered or me not be sure if the recipient saw them.

Replying to @⁨crandall@lemmy.today⁩

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

Fewer Letters More Letters DNS Domain Name Service/System IMAP Internet Message Access Protocol for email ISP Internet Service Provider LXC Linux Containers SMTP Simple Mail Transfer Protocol TLS Transport Layer Security, supersedes SSL VPS Virtual Private Server (opposed to shared hosting) k8s Kubernetes container management package

[Thread #106 for this comm, first seen 19th Sep 2026, 02:10] [FAQ] [Full list] [Contact] [Source code]

Hachyderm.ioImran Nazar ~ عمران نزر (@Two9A@hachyderm.io)3.05K Posts, 306 Following, 284 Followers · Front-end #typescript developer and general keyboard tapper; author of Internet RFC 7168 (Hypertext Coffeepot Control Protocol for teapots); occasional plumber, more than occasional #c64 #retrocomputing enthusiast, terrible at classical #piano. Header photo is a verdant scene looking over the landscape near Buxton, England, taken from a single-track country road.

Replying to @⁨crandall@lemmy.today⁩

I picked zoho.com free tier, with an eu.org domain after scanning through a set of different options. No marketing appended to emails and only throttles on excessive sending instead of hard limits. Each service sends from its own address.

purelymail.com was my backup paid option if the free plans were no good, with the advanced pricing and low usage the cost would be miniscule.

Replying to @⁨crandall@lemmy.today⁩

If they’ll go for it, the most reliable way will be to offer them extra email addresses on your mail server. Sometimes, when a mail provider decides they don’t trust an incoming email, they don’t mark it as spam or reject it and send a notification response. They just… Silently drop it without ever mentioning it to sender or recipient. The only genuinely reliable way I’ve heard to build and maintain the reputation to avoid that is to send way more mail than a few individuals can manage, even with your services sending notifications. Theoretically, you can do it with really low mail volume if you jump through a whole bunch of hoops, but nothing is really guaranteed long term.

Replying to @⁨crandall@lemmy.today⁩

I run a small email host, so biased a little bit. For the app-notification half, don’t put it on a mailbox host at all: smtp2go or SES, the way people are already saying here, is the right shape, because your services want an authenticated relay and nothing else, and outbound 25 is blocked on most residential lines and a lot of VPS providers anyway. The part that genuinely needs mailboxes is the friends-and-family half, and it’s worth separating: one host for the humans on your domain, one relay for the machines, so a noreply@ reputation problem never lands on the addresses people actually read. If you want FOSS on both sides, maddy is the honest answer and someone above already gave it. If you decide the human half isn’t worth running yourself, I wrote up that tradeoff at franklymail.com/vs/self-hosting, with the caveat that we’re paid and not FOSS, and we deliberately don’t do app or bulk sending, so it only answers half your question.