this post was submitted on 10 Aug 2023
35 points (94.9% liked)

Selfhosted

40708 readers
438 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I'm exploring some options to see if it's viable to self host my email account. Currently I have:

  • A home server that I can host the entire email stack but I cannot open the SMTP port there
  • An AWS account where I can create a VM with SMTP ports open to the internet and reverse DNS support, also I have a domain and AWS SES configured and approved to send emails

Ideally I would want to send and receive from my home server, but that is not possible, so I'm exploring some alternatives:

For receiving emails:

  • Cheap VM with postfix and my home server with dovecot, essentially forwarding all emails to my home server where I want them to be. I don't know if this setup works tho.

  • Keep everything in a VM, with the downside that I'll need to do extra work there as it will have all my data. If possible I don't want to go that route.

For sending emails:

  • Sending from the same VM receiving emails, and have everything managed

  • Use AWS SES to send emails in my behalf

Any input or opinion is appreciated. I'm currently exploring options, I haven't made any decisions, so if you have a better alternative feel fee to share.

Thanks!

you are viewing a single comment's thread
view the rest of the comments
[–] sirdavidxvi 14 points 1 year ago (3 children)

Just passing along what I've read many times: that self hosting email can be difficult. Particularly sending, because the large providers tend to treat email from less known sources with more skepticism (such as by marking as spam), even with properly configured SPF and DKIM.

And if your server is down, you may miss any incoming mail for the duration. I don't know if other providers would try resending after a period of time if the receiver is unreachable, but I doubt it (just an educated guess).

I love self hosting services but email is something I've decided not to touch with a ten foot pole.

[–] Chobbes 2 points 1 year ago* (last edited 1 year ago)

It’s harder than a beginner would expect, but also not as bad as everybody says. It’s doable and we shouldn’t discourage everybody from trying it (but don’t use it for anything important until you’re sure it works). Just make sure you set up SPF / DKIM / DMARC and rDNS properly and you’ll most likely be fine. If you’re scared or frustrated you can use a relay for send. Receiving is easy.

[–] subtext 1 points 1 year ago* (last edited 1 year ago)

To be fair, the SMTP RFC (5321) says that senders MUST retry sending upon a failure (source), but it only specifies that they SHOULD have a retry of 30 minutes, and an even weaker recommendation to continue to try for 4-5 days before giving up.

[–] sirdavidxvi 1 points 1 year ago* (last edited 1 year ago)

Just a quick add: even for my self hosted services, I configure Postfix with Mailgun for SMTP relay for alerts and whatnot just to ensure delivery to my external mail provider.

Edit: a few words for clarity