https://www.hetzner.com/de/webhosting
Just because you can (theoretically) run your own infrastructure does not mean you should. Trust the professionals. You don't do your own surgeries, do you?
(not affiliated to Hetzner, just was the first offer I thought of.)
It's still putting all your eggs in one basket in a sense, but being a paid service there's a sense of privacy, security, and permanence that Gmail and the other free providers don't offer. I do own my own domain as well, and I have mail accounts tied to it that I use for certain services and communications, mostly medical and local businesses, but I'm still at the mercy of my hosting provider for that domain. With that said, my provider (Tiger Technologies) has been astoundingly awesome and has never let me down in 12+ years of service.
As a learning experience, sure, but most people are not prepared for what running a 24/7 mail service requires of them.
First of all, a static, non-residential IP is likely needed. The big players will flat out refuse receiption if your IP is registered as residential, so that rules out hosting it from your home despite having gigabit internet.
You also need SPF, DMARC and DKIM working, or major players will also flat out refuse reception.
On top of that, you need to implement the infrastructure to actually host a server 24/7, including patching and backups, as well as monitoring it for unauthorized access.
Despite all of the above, you may still find yourself on a spam/block list, and removing yourself from these can also turn into a large task.
Part of the irony of Gmail having outages is that Google and other "large players" have fought long and hard for a decade to make it harder to host your own mail server. It has been done in the name of fighting spam, but i doubt any of them minded it making it harder to run your own.
So yeah, build your own mail server as a learning experience. Then move the domain to someone dedicated to running it.
I purchased a lifetime subscription (limited promo offer) with mxroute.com. 10GB mail storage, unlimited domains and accounts (limited by space only), as well as a Nextcloud instance for all your users. Service and uptime has been nothing but exceptional. Customer support is actually reachable. The only downside is that the spam filter (SpamAssassin IIRC) is not as highly trained as the GMail one, so more spam comes through.
Downtime hasn't been a major issue - senders will retry sending email, usually multiple times over several days. I've been able to have downtime of 24-48 hours without losing any messages.
A SPF record is just another easy to create DNS entry. If you know how to manage DNS, setting up SPF is a matter of minutes. DKIM is just slightly more complicated, with an extra key generation step. Sites like mxtoolbox.com can help you validate records.
The biggest problem I think I have with my own server is security. I do patch the machine regularly, but of course I don't have the same kind of security that Google or another big player would. On the other hand, I suspect I might have a smaller attack surface and better security than plenty of small websites.
If you want to directly send mail that's true. But if you send mail through a smarthost, like your isp's smtp server, you can easily receive mail on a dynamic, residential ip.
> implement the infrastructure to actually host a server 24/7,
email is really tolerant of downtime. You can be down for hours without losing mail. The sending servers will retry for a while.
I’m aware senders will retry for days if your server doesn’t reply, but it still requires monitoring and is not just a “fire and forget” solution.
Also, if your server starts bouncing emails, chances are you’ll be missing mails. Again, needs monitoring.
At the risk of stating the obvious, note that 'lifetime' refers to the lifetime of the company, not the customer. Which underscores the risk of buying lifetime subscriptions.
And as much as I like the idea of avoiding recurring costs (I have a 'lifetime' Plex pass), it seems to me that these can't be sustainable for the company on the long term.
It’s really no different than Google, where a single bad comment somewhere in their vast eco system can end up getting your account banned.
In my case I try to stay as far away from Google as I can with my everyday services. I’m also well aware that chances are extremely high that any email I send will make its way to Googles servers.
The “easy” solution would be to self host, and I do that to some extent, but as I work with system administration I really don’t want/need another day job. I’m actively looking for relatively secure, privacy aware and affordable cloud solutions for everyday use. I wrote affordable because nothing is free.
Spam filters have been content driven for a long time now. IP addresses and domain names are ephemeral and so are 'blacklists'. With the amount of spam being send, we would have blacklisted the entire internet by now.
If a spam filter gives false positives, it hurts the receiver just as much as the sender.
The real problem with self-hosting is that the majority of self-hosted e-mail servers are terribly configured. Getting the SMTP server running is one thing, but getting DKIM, DMARC, SPF, TLS and MTA-STS running properly is often overlooked. What was the last time you checked the validity of the TLS certificate of your SMTP server?
Get your server and domain setup properly. Sign your email with DKIM, setup an SPF and DMARC policy and perform DMARC monitoring to spot problems. Setup TLS and an MTA-STS policy service for your incoming email. Throw in SMTP-TLS-reporting for good measure. E-mail servers are not set-and-forget if you want to do it right. And this is not the fault of large corps, it's the spammers who got us in this situation.
It's really easy to blame large services or blaming your email deliverability problems on being on the same IP block as a spammer, but really it's almost always a misconfiguration on your side.
Disclaimer: I'm the founder of Mailhardener (https://www.mailhardener.com), we do e-mail hardening and solve deliverability issues.
I also run my own and its been easier than expected, especially with maddy: https://github.com/foxcpp/maddy
I'd still suggest to put "secrets" in a free global trusted email provider with 2fa
Services also tend to be better if lock-in effects on customers are low. ... and using your own domain for email does reduce lock-in significantly.
unrelated: the link in your profile does not seem to work.
But there is a case for making legislation forcing email providers to allow moving emails to other providers (how it should be done technically is another question). This is already in effect for telephone numbers many places.
As such, migrating these email addresses was easy enough.
My older @gmail and @googlemail ones though, not so easy. I've been moving each account I have used with these addresses one-by-one, but you never catch them all and even when you do, some services simply will not let you change your email address.
I recall being so excited when Gmail first launched and was one of the first people to get a Beta invite. I regret ever signing up for them now, given the headache it has been to get off it.
The main thing here is to avoid single point of failure as in both domains (politically induced problems) and infrastructure (technically induced problems). If people would use more than just a handful domains/providers for mail then single failures would not have that big of an impact.
I have been hosting my mail on my own domain for the past 3 years and have not been impacted by this incident. Currently I am happy for protonmail that I use to host my mails at. But I know that I can easily move on, if service drops, and even selfhost.
and the weight of google as well!
an individual mail getting onto an blacklist is most often than not a dead sentence for the address, the domain and sometimes even the ip.
but if google is at fault and email get into a permanently removed bucket, like in this event, it's in the interest of the other to play nice and accommodate for the fault.
I think people severely underestimate how hard it actually is to consistently deliver email in 2020 between dkim, spf and domain keys while tiptoeing around everyone else ip/email antispam services.
But the next best thing you can do is simply just use your own domain. That way, you can at least decide to migrate your email elsewhere. Don't use the free domains you get from things like gmail or other providers, because then you have to _change_ your email address, and not just your MX records.