3 ms·
They should do PGP on the way in, for people who want it. It's trivial to set up. All they need to do is let people paste in a public PGP key and encrypt all in
by mike-cardwell 9y ago
They should do PGP on the way in, for people who want it. It's trivial to set up. All they need to do is let people paste in a public PGP key and encrypt all incoming email with that key. Here's how I've been doing it for the last 7 years:
https://www.grepular.com/Automatically_Encrypting_all_Incoming_Email https://www.grepular.com/Automatically_Encrypting_all_Incomi...
- dewey 9y agoIf it would be "trivial to set up" don't you think they would've already done it and offer it as an option?
- mike-cardwell 9y agoWell, it is "trivial to set up" as per my link, and they don't offer it as an option, so apparently not. Perhaps they don't think enough people use PGP to make this a worthwhile option to add. But given the service they are offering, it seems like an obvious feature and quick win to me.
- dewey 9y ago"trivial to set up" on your own mail server with you as the only user is slightly easier than rolling it out to thousands of customers, testing it, make sure backups are all working, write documentation for users, collect public keys of users, ... You can't just add a single line with your perl script to production and hope it works for everyone...
- mike-cardwell 9y agoIf you are already providing complicated features to N customers, then adding one simple feature for those N customers is trivial. If that isn't true, then all features are non-trivial to add and you've built your systems and processes badly.