Which is fine. But self hosting has multiple complexities. It's not just a case of installing and configuring a mail server. Maintenance, security, electric costs etc just add up.
I'd sooner have working emails and leave all the management to the provider.
I know internally Broadcom is screwing over VMware employees with new contracts. I've heard of staff pushing back three times so far to get contracts changed.
You can work around the need to go around updating all sites with your new email address... at least the next time you need to change your email address.
I use SimpleLogin to create a unique alias (on my own domain) for each website. When I finally migrated to Proton all I had to do was add the proton email address to SimpleLogin and delete my old GMail address to get it to point to Proton (I started migrating to aliases before moving away from GMail). Likewise if I ever move in the future I only need to update SimpleLogin. I was looking to move to Skiff when my Proton renewal was due!
To set this up I had to obviously update every single website which was very time consuming. However I have much better protection now as email addresses are disposable should a site start spamming me. The only site that actually knows my Proton email address is Bitwarden, Proton itself and SimpleLogin.
Looking in my account I have over 300 aliases. Crazy.
I liked Skiff but moved to Proton as Skiff was still too new for me to trust at the time. Glad I went with my instinct.
Shame though when people are actively taking their privacy seriously and getting away from the major free providers.
Their free tier storage offering was amazing. I honestly couldn't see how they could offer so much for free. I was very tempted at the time but chose proton. Although I think I may move to Fastmail when my renewal is due.
Regardless of who you choose. Use an aliasing service. It makes moving to a new provider/email address a breeze on the future. It took me days to go around updating all my 200 sites online. If I ever move from proton it will take me 5 minutes to ensure all my sites now go to my new provider.
My only tip would be to create a new domain rather than using a shared one. This will prevent some sites from blocking you from using an alias.
Awesome info! I wasn't overly happy with having to use CloudFlare for just this one feature. I'll have a test with my registrar.
The CNAME flattening is not a regular feature of DNS, so I have to use Cloudflare. Maybe other providers do the same, but I haven't looked around. It's certainly not something namecheap offer.
I point my TLD to the dynamic DNS record and then point to other records to the TLD as CNAME records. I'm using Nginx Proxy Manager to reverse proxy traffic to different services. These all live on a Raspberry Pi 4.
I don't have a static IP but host services off my paid domain. I use duckdns and point host records to the duckdns address. I have to use CloudFlare to manage my DNS records for this to work.
Pi OS. It's a Pi4 after all.
I have a Pi4 that runs a couple of services to run in the house. Even this still needs regular OS patching, updated images pulling, troubleshooting etc.
I ran my own mail server many years ago but I can't reliably do one anymore. Besides, death can happen at any point and I'd hate to leave my family with email mailboxes that are just gonna stop one day from something breaking or a domain not being renewed.