this post was submitted on 17 Sep 2026
43 points (100.0% liked)

Selfhosted

62167 readers
263 users here now

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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] mlg@lemmy.world 1 points 19 hours ago

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.