3.1.7 fixed it for me
Enigmail version 3.1.5 OS/CPU=Linux x86_64 Platform=X11 Non-default preference values: keyCheckResult: {"expiredList":[],"lastCheck":1700548217638} configuredVersion: 3.1.5 juniorMode: 0 cryptoAPI: 1 advancedUser: true displaySignWarn: false lastUpdateCheck: 1700548271 agentPath: /usr/bin/gpg2 protectedHeaders: 0 dom.workers.maxPerDomain: 512
edited my previous post - a sample key and more information from the log
I just encountered the same problem. The debug log (and console) shows Enigmail looks up the email address from the keyring just fine BUT then says that no key with enough trust was found .. so the encryption/signing fails ... A work around for urgent individual addresses is to use the Enigmail preferences. Choose the Key Selection tab, then 'Edit Rules'. This is where you can Add a rule for the target email address to match a selected PGP public key.. It looks like this creates a config (json) entry...
I just encountered the same problem. The debug log (and console) shows Enigmail looks up the email address from the keyring just fine BUT then says that the ID has no public key .. so the encryption/signing fails ... A work around for urgent individual addresses is to use the Enigmail preferences. Choose the Key Selection tab, then 'Edit Rules'. This is where you can Add a rule for the target email address to match a selected PGP public key.. It looks like this creates a config (json) entry which...
I just encountered the same problem. The debug log (and console) shows Enigmail looks up the email address from the keyring just fine BUT then says that the ID has no public key .. so the encryption/signing fails ... A work around for urgent individual addresses is to use the Enigmail preferences. Choose the Key Selection tab, then 'Edit Rules'. This is where you can Add a rule for the target email address to match a selected PGP public key.. It looks like this creates a config (json) entry which...
Solution is shown at the end of this bug report.
See the solution at the end of this