recipient not trusted / cannot create per recipient rule
OpenPGP addon for Mozilla Thunderbird
Brought to you by:
pbrunschwig
Menu
▾
▴
Hi all,
please give me some advice how to use Enigmail in order to encrypt automatically.
I got a valid key now. However, encryption does not work as expected
1) "send" - this pops up the window with the information "Recipients not valid, not trusted or not found
0x9A614....: No valid key
I then do select him and myself, since I do send a Bcc to me.
Enigmail tells me:
You have selected a smaller number of keys than recipients. Are you sure that the list of keys to encrypt is complete?
Why that? Then sending works
2) why doesn't Enigmail mark the recipients automatically?
Why does Enigmail assume to take another key, which is not valid?
The message came with a good signature for Key ID: 0xED58653C / Signed on: 12.02.18, 18:42
When I do reply, why does it try to use 0x9A614...?
3) per recipient rules
The window offers the button to create a per-recipient rule. But when I click this button, the same window opens again.
4) send button disappears
why does the send button disappear after these actions? It's greyed out and no longer available. It comes back after I save the message.
Last edit: Martin Trautmann 2018-02-12
This looks like you have a per-recipient rule pointing to a wrong key. Go to menu Enigmail > Edit Per-Recipient Rules and search for your email address, then delete or edit the rule.
Hi Patrick,
this and the other issues have been resolved by now (Thanks O.!)
FYI what went wrong:
Thunderbird preferences contained an ancient PGP key id, which never showed up within usual preference handling. This key was included for every new account.
This old key id was used always, too.
* As a strange side effect, the problem appeared only if I had myself within the BCC, but not otherwise
What made the understanding complicated: usually only 8 Byte keys are shown. But within the complaints long key ids were shown, where I did not regognize the short part.
In Key Manager dialogs, 8-digit keyIDs are also used quite often.