On 30/12/16 07:43, Ludwig Hügelschäfer wrote: > Hi, > > On 30.12.16 03:52, Pedro Ribeiro wrote: > >> Hi Ludwig, >> >> I've added a default-key directive to my gpg.conf and got it working. > > Enigmail does not need any of those directives in gpg.conf to work > properly. The other way round: they lead to problems if you e.g. change > keys and forget about old entries in gpg.conf. > > If you ADD such an entry in gpg.conf and it fixes things for you shows > that something is misconfigured in your Enigmail setup. So, if you don't > mind, I'll ask the other two questions again: > > Do you have a per-recipient-rule for your email address? Did you specify > the new key in account settings? > > And another one: Did you specify the new key for all identities of the > account(s) configured to use with Enigmail? > > Ludwig > > > > > > _______________________________________________ > enigmail-users mailing list > [email protected] > To unsubscribe or make changes to your subscription click here: > https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net >
I used to have a per-recipient rule for myself, but deleted it and I've tried with and without it. My gpg.conf did not exist before I added the default-key directive. I only have one identify for this account, and he new key is specified in the Thunderbird -> OpenPGP Security account settings. Enigmail is set to use convenient encryption settings. My gpg-agent.conf says this: ###+++--- GPGConf ---+++### default-cache-ttl 600 max-cache-ttl 6000 But the PIN still doesn't get cached... Regards, Pedro _______________________________________________ enigmail-users mailing list [email protected] To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
