```To prevent theft of correspondence (in the event of a compromised account or server) the messaging service must store only messages that have not yet been delivered or returned as undeliverable.
Where archiving is required, the service should encrypt the traffic of designated accounts with a public key, and forward it to a write-only archive service.```
This is a silly default behavior. For enterprise I guess it makes sense, but I want to keep my mail local, not shuffle it off to Yet Another Service™. And I certainly want it to SAVE my mail and not delete it by default!
Someone will create a web service that implements a TMTP client to replicate your account in the cloud. That's fine for many consumers, but must not be the default.
I guess the answer is obvious. Sorry, I didn't read this properly. Good work on this!
Thanks for the encouragement!
Follow mnm: https://twitter.com/mnmnotmail :-)
For 25 years you've pleaded for an SMTP replacement. But all you got was SaaS, sans interop.
Now at long last, here it is. (We're so sorry it's taken so long, but we're only human!)
TMTP is a sane network protocol for email, to end attacks and promote productivity. You can download client and server, written in Go, from the mnm open source project:
Why now? The cybercrime crisis, a huge portion of which is facilitated by social engineering attacks via email.
