Most likely a private key is not found. Thus only keys generated within the program with "weaker" cryptographic properties are used. A related discription is stated here https://superuser.com/questions/1112673/gpg2-no-secret-key gpg version gpg (GnuPG) 1.4.20) does not work fully. Will later dig into some details, using gpgv2 or gpg2 would be recommended I think. But not sure about this. libetpan binding should further be better explained, make install somehow does not work.
What has this got to do with Claws Mail? Please explain a little more verbosely.
(In reply to comment #1) > What has this got to do with Claws Mail? Please explain a little more > verbosely. Reproduce with installing gpg and gpg2 sudo apt-get install gpgv gpgv2 gpg2 --gen-key and follow instructions with correct mail adress If you search within configuration -> account settings -> plugins -> gpg you will not find your new key. If you create your key within claw mail with help of the plugin, lets say for my mail adress and you list it with gpg2 --list-key max_muster it is rsa2048 and has no expiration limit. Expiration limit and abit longer key is recommended. Further it is annoying that keys are not found. I am unsure about the exact formatting and where what key is saved. Further I have no idea about the plugin used/how the binding/linking works.
(In reply to comment #2) > If you search within configuration -> account settings -> plugins -> gpg > you will not find your new key. Where are you expecting to find it, why are you expecting to find it, and what are you expecting to find?
(In reply to comment #2) > If you create your key within claw mail with help of the plugin, > lets say for my mail adress and you list it with > gpg2 --list-key max_muster > it is rsa2048 and has no expiration limit. > > Expiration limit and abit longer key is recommended. > Further it is annoying that keys are not found. If you don't like the key that is generated from within Claws Mail, then don't generate a key from within Claws Mail. I'm still not seeing the bug here.
Alright, missing configuration of gpgv2/gpg2 [with missing libgcrypt] does not work. calling gpg2 --version returned [ libgcrypt is too old (need 1.7.0, have 1.6.5) ] and thus was not correctly installed/linked and I fixed this with # echo "/usr/local/lib" > /etc/ld.so.conf.d/gpg2.conf && ldconfig -v Therefore the key could not be found. -> not related related to this plugin Mentioning gpg2.x as dependency in the plugin description would be great though. More particular gpgv2 as ubuntu/debian package. Editing and creating key with gpg1.x does not work (at least for me).
(In reply to comment #5) > Alright, missing configuration of gpgv2/gpg2 [with missing libgcrypt] does > not work. calling gpg2 --version returned [ libgcrypt is too old (need > 1.7.0, have 1.6.5) ] and thus was not correctly installed/linked and I fixed > this with > # echo "/usr/local/lib" > /etc/ld.so.conf.d/gpg2.conf && ldconfig -v > Therefore the key could not be found. > -> not related related to this plugin > > Mentioning gpg2.x as dependency in the plugin description would be great > though. > More particular gpgv2 as ubuntu/debian package. > Editing and creating key with gpg1.x does not work (at least for me). That's a distro error, nothing to do with Claws-Mail. gpg1.x works fine.