Leaving python-dev behind
Leaving python-dev behind
Posted Jul 25, 2022 16:06 UTC (Mon) by Avamander (guest, #152359)In reply to: Leaving python-dev behind by pizza
Parent article: Leaving python-dev behind
Getting email right is in reality really difficult. Subtle things can topple the entire stack, how many can afford that with a thing they really use? "Not entirely friction-free" is an understatement in this context. I'm not saying it's not possible, it absolutely is. But the unfortunate nuance here is that it has been *made* difficult. Just just like people find using e-mail archaic at times, hosting it is that times ten for no good reason.
I've heard "oh but it's because email is complex", but that phrasing I don't agree with. If we take one of the most basic things, TLS, we can really see the stark contrast. In the "web ecosystem" we've got multiple webservers with ACME clients built-in, in the email world there's one (maybe two) projects like that and they're not finished. Point being, now imagine a full mail server that can get its own TLS certificates, update its own DANE, MTA-STS, DKIM (ARC) or even A and SPF records. Totally doable, but there's a resistance or an attitude that hinders most improvements (QoL included).
One can feel this resistance well once you do become a mailop. There are large email providers (e.g. Deutsche Telekom) that intentionally doesn't publish a SPF record, wow what "fun" it is to filter spam from @t-online.de. It's just one example of the mindset, there are many more and it has gotten us the monstrosity that is e-mail at this point in time. It could be much better, I really wish it were, but unfortunately right now I can only see monopolistic megacorporations really pushing things further.