Someone needs to create an SMTP for the 21st century. Something that forces servers to:
- Refuse to relay a message without end-to-end encryption and a digital signature
- Require unknown senders to solve a cryptographic hash problem per message
- Require a TLS certificate from a CA on both sides of any connection
- Use 8-bit attachments (no Base64)
- Drop HTML in favor of Markdown
- Not support external embedding
@thor
- signing every single email is a bad idea, sometimes you do *not* want non-repudiation
- CAs are a scam and lack trust agility
- SMTP has nothing to do with the contents of the message, so your last three points have nothing to do with SMTP
@aleksejs Disagreed.
@thor sounds like you just did. Have fun emailing yourself.
@thor lololololololol
@thor - That's DIME - https://darkmail.info/ - Ladar Levinson is still working on it daily. Has a small team. It's awesome, but they lack funding and, more importantly, management. If you know a technical project manager who is willing to volunteer their time, they could use it.
@tinker Can't look at it right now, but my first problem with it is that it doesn't seem to be an IETF draft or RFC? You need to get the vendors involved, like with HTML5.
@thor - Fully agree. - Specs are here when you get a chance. Would like your input. https://darkmail.info/downloads/dark-internet-mail-environment-march-2015.pdf
@thor - Note! PDF
- Support folder attachments
- Support compressed attachments
More generally, 21st century email should:
- Support mailing lists on the protocol level
- Support filter rules on the protocol level