-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 24.04.14 20:52, Mike Acker wrote: > On 04/23/2014 10:33 PM, Daniel Kahn Gillmor wrote: >> FWIW, i fully agree that the right place to fix this misbehavior >> is in GnuPG itself, not in enigmail. I care about non-enigmail >> users of GnuPG, and i definitely don't want to have the headache >> of synchronizing key selection routines of multiple GnuPG-using >> applications. > gnupg doesn't have access to your email directory. it has to be > corrected in enigmail which, as noted, is why they have per > recipient rules
It's interesting to see why you all seem to know why I implemented per-recipient rules ... ;-) The truth is this: the reason was convenience and laziness: I wanted have a user-friendly system that allowed me to activate encryption based on rules, such that I would not have to care about enabling encryption or signing anymore. Nothing more, nothing less. - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEVAwUBU1t8N8k25cDiHiw+AQhVOQf/cb2lNoikVxhPmbjioQwlJg5bvHC6fMRd DAVWoMWT+ZhfXlg7chh6sEsqlNqOMfGeE1+O0tYa8DK7Qb/mD/Tw15rZmH5eOcP7 oyNNhwpLkW3eUPr/Jqp4c1lEwhucF19GZGBu6pQFuLC49QF3HfdNSk/wnmv9Ql2z uxytNgIcAsTda85Yz0rtZoAT5w5pclFVwpytBgI7i/D5sByJri5ffuADDS4Rh56c VrqvV6kZMJwzPOikccDsM5Z95gYC9vvBV99Mv0MjgfDVXxXuAeaSViXSMMWt7pIw NKjLAMSt5jvDhWzs3helrIPKua9KuaCgaVQo8td49oz5mGVWFcSwRg== =i0/x -----END PGP SIGNATURE----- _______________________________________________ enigmail-users mailing list [email protected] https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
