When attempting to send an email using an account with multiple matching keys, this message appears: Could not queue message for sending: Signature failed: Secret key specification is ambiguous In my case, there are two distinct keys. The case of a debian maintainer with one key in two keyrings might also be relevant: https://gitlab.com/muttmua/mutt/merge_requests/43 I would appreciate a key-selection prompt. With that, there's a risk of picking a different key from what's been used for previous communication but it would restore the ability to send emails. Official Arch Linux package - if that matters.
Can confirm this bug using version 3.17.4 in Fedora Linux. I created another gpg key in my local keyring today and when trying to send a signed mail, ClawsMail complains with the same error message as in comment #1. It would be beneficial if the PGP plugin could either use the value of the "default-key" keyword in ~/.gnupg/gpg.conf (I would prefer this one) or let the user chose the default key inside the plugin's options. The same bug is also mentioned here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214216
> It would be beneficial if the PGP plugin could either use the value of the > "default-key" keyword in ~/.gnupg/gpg.conf (I would prefer this one) or let > the user chose the default key inside the plugin's options. You can make these choices in your Account preferences, under Plugins/GPG If you want the account to use the key cofigured as 'default-key' in gpg.conf then you choose the option in Claws Mail 'Use default key'. If you want to use another key other than the default, then use either 'Select key by your email address' if you have one secret key that can be idenitifed by your email address. If you have a secret key that cannot be identified by your email address in Claws Mail, or you hav multiple secret keys associated with your email address, then use the 3rd option 'Specify key manually' and enter the key id. I have several scret keys used for different accounts in Claws Mail and use them all without problems when using the above methods to associate a key with an account.
Ups, I did not have a look into the account options. Sorry for that. I only looked into the general GPG preferences. With your help I found the option you mentioned. And yes, I can confirm that when choosing "Use default GnuPG" key, it uses the one which is set in my gpg.conf. (It was set to "Select key by your email address" before). This bug can be closed from my point of view. Thanks allot!