Re: bbdb, encryption

[David Maus <dmaus@ictsoc.de>]

Hi Michael,

I don't have many contacts that utilize GnuPG but for the ones I have
I simply let SEMI decide about the key to use based on the recipient's
mail address and make a deliberate decision whether to use encryption
or not.

Maintaining an association of contact and key id in the addressbook
seems like unnecessary work to me because this association is already
stored in the keyring (at least in my case).

Auto-encrypting messages based on a flag in BBDD might look like a
good idea on the first glance but in my experience it is not worth the
trouble.

To implement it you should look for an appropriate hook in WL and then
decide whether or not to encrypt the mail by reading the recipients
and matching them against the BBDB entries. If the message can be
encrypted to all recipients you toggle encryption and hope for SEMI to
find the keys in the keyring.

Best,
  -- David


At Sun, 21 Sep 2014 10:01:23 +0200,
Michael Welle wrote:
> 
> Hello,
> 
> I have extended bbdb v3 with an attribute holding the gnupg key of the
> entity described by the bbdb entry. As a default I want to encrypt
> emails to entities that have this attriute set. Any opinions on this?
> Is it worth the effort? Has anyone a similar scheme in use?
> 
> Regards
> hmw
>