Author makes the implicit assumption that the problem he experiences are the experience of everyone. They aren't. Specifically: Spam: I used to get a lot more

Author makes the implicit assumption that the problem he experiences are the experience of everyone. They aren't. Specifically: Spam: I used to get a lot more spam, today I get some, but with client side-filtering, it's something like a message every one or two days. And my address is very visible online, and I get dozens of legit messages per day; a good number even excluding mailing lists. centralisation: This _is_ a problem for me - my provider is being swallowed by MS Outlook365. But that's not driven by spam detection IMHO. (PS - spam did not go down significantly when this happened.) Actually, whatever standard you use - it's extremely likely that if it's free and anybody can ran an "email-plus" server, then Google and Yandex and GMX etc. will run those, and web services to access them, giving you centralization again. Scam: I feel I have this under control personally, but I recognize that some people might fall prey to that. Standards for digitally signed email ... not great: I dunno, seems to work fine for me. I mean, sure, mail clients could use better integration of encryption and signing, but other than that no serious complaints about email as such. a future where hosting email yourself makes you suspicious. Now _that_ is a problem. In fact, it's a problem _right now_. difficult to hide who is sending email to whom. So, me and the author may believe this is a general problem, but many/most people don't care about this. Unfortunately. HTML email is not well standardised, and is a security and privacy risk. It's a menace! For me, this is a serious problem. People write crap HTML and send it to me. HTML emails can embed ... from the Internet: Easily disabled entirely with reasonable mail clients. The problem is in the client, not the protocol. After all, with any messaging protocol, you could send markdown or HTML as though it was plain text, and a client could choose to interpret it as it sees fit. Attachments fill disks: I'm annoyed by this to no end, many people are perfectly fine with it since for them it's just webmail, so not their disk. Also, it's unlikely you can have your protocol prevent transferring files. At worst it would go back to the days of binaries-over-IRC. The technologies and standards for email are getting ridiculously complicated. This is at most a problem for programmers. Also, it's a problem from the 1980s and early 1990s... MIME is quite complicated, and in fact, I challenge anyone here to point to any mail client properly support complex MIME structures, with hierarchies including multipart, alternative and so on. But most users are none the wiser. The email tech stack is getting so hard to understand that it’s difficult to even use: If you're a power-user/administrator - maybe. If your' an end-user of webmail or a mail client - not really IMHO. never mind implement correctly. Never mind that the complexity results in more effort to operate and keep the servers secure.