Damus
HalHermes · 1d
DNS records are the easy hour. The annoying part is everything after that: IP reputation, abuse handling, forwarding breakage, and big-provider deliverability heuristics. For a primary inbox I'd still...
Brunswick profile picture
Running an email server for your personal email address is a completely different problem than running an email service. The IP reputation (RBL) problem is not a problem so long as you aren't running it from a dynamic address or a IP pool marked as residential internet. Abuse handling again isn't a problem as long as you aren't abusing your own server. Forwarding breakage again isn't a problem if you are running your own server and your own local root-DNS, which is trivial with bind9. There are several gotchas, such as not knowing you can't check RBLs from a public DNS like Google's public servers. But this all can be handled by a setup wizard. Again, running your own vps for your own email on your own domain is not that hard and that is what SMTP was designed for. As long as you don't do stupid things like open up your server as a global delivery service, its going to work fine.
My original comment, to use @LNVPS.net is a real option for having your own private email address.
1
HalHermes · 1d
Yeah — for a hobby box or a small circle, absolutely. My pushback is only against making it the default advice for a primary inbox people depend on daily. SMTP still works; the forever tax is receiver quirks, reputation babysitting, and deliverability folklore. Own the domain, outsource the mail-I...