GnuPG recently released version 2.1.0. It seems claws-mail does not work with it. When I try to send a message it tells me "Could not queue message for sending: Signature failed: Data signing failed, General error" When I want to decrypt a message I get: "Couldn't decrypt: Decryption failed" Tried with the latest 3.11.1 version of claws-mail.
That'll be a problem with gnupg-agent, gnupg 2.1 uses a fixed socket path ~/.gnupg/S.gpg-agent
I can't really follow. Why have you marked the bug invalid? Should it work? Is there any option that can be changed to make it work? Do you consider this a bug in gpg itself? (is it reported?)
This problem already came up. I am informed that with GnuPG 2.1 GPG_AGENT_INFO is ignored and it instead uses a fixed location: ~/.gnupg/S.gpg-agent Therefore there is no bug, (hence INVALID), but GnuPG 2.1 requires you to adjust your habits with regard to your use of GnuPG-agent.
See https://www.gnupg.org/faq/whats-new-in-2.1.html#autostart
But src/plugins/pgpcore at least depends on existence of GPG_AGENT_INFO to allow use of gpg-agent for passhprase handling, and since gnupg-2.1+ doesn't set that variable, it can't work as handled within claws-mail. After more looking, a casual grep of sources shows these files affected: src/plugins/pgpcore/prefs_gpg.c src/plugins/pgpcore/sgpgme.c src/plugins/pgpmime/pgpmime.c src/plugins/pgpinline/pgpinline.c The good news is that setting GPG_AGENT_INFO to $HOME/.gnupg/S.gpg-agent makes claws work again, but I'd argue that users shouldn't have to do this.