this post was submitted on 10 Aug 2023
33 points (94.6% liked)

Selfhosted

40152 readers
472 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 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
33
Email server hosting (lemmy.brennoflavio.com.br)
submitted 1 year ago by brenno@lemmy.brennoflavio.com.br to c/selfhosted@lemmy.world
22 comments fedilink hide all child comments
 

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
[–] thatsnothowyoudoit@lemmy.ca 6 points 1 year ago* (last edited 1 year ago) (1 children)

As someone who runs a self-hosted mail service (for a few select clients) in AWS, this comment ring true in every way.

One thing that saved us beyond SPF and DKIM was DMARC DNS records and tooling for diagnosing deliverability issues. The tooling isn’t cheap however.

But even then, Microsoft will often blacklist huge ranges of Amazon EIPs and if you’re caught within the scope of that range it’s a slow process to fix.

Also, IP warming is a thing. You need to start slow and at the same time have relatively consistent traffic levels.

Is it worth it, not really no - and I don’t think I’d ever do it again.

[–] brygphilomena@lemmy.world 2 points 1 year ago (1 children)

I think this is largely why people complain that email hosting is so difficult. It's not the hosting, it's that so many people are doing it with a cloud hosting providers IP space. AWS, Azure, and Digital Ocean all tend to have their IPs in at the very least grey lists. Many home ISPs DHCP scopes too.

Getting a proper static IP, your own subnet from ARIN, or finding a colo with their own IP space will give people much better results.

[–] stown@sedd.it 2 points 1 year ago

What would it take for a residence to get an ARIN subnet?