Hi, seems to be a GPG 2.0.x issue with large keyrings. I opened https://bugs.gnupg.org/gnupg/issue2297 some time ago.
Try GPG 2.1.x as this helped. Cheers, Michael On 23.11.2016 17:16, Anthony Papillion wrote: > On 11/23/2016 10:05 AM, Patrick Brunschwig wrote: >> On 23.11.16 16:52, Anthony Papillion wrote: >>> When I tell Enigmail to refresh all of my public keys, I /always/ get >>> the message at the end of the operation that says "keyserver refresh >>> failed: bad public key". >>> >>> I'm assuming that I receive this message because a few of the keys in my >>> keyring are not on the public keyservers but I don't know for sure. When >>> I go through the other details, I see no errors of key fetching so I >>> don't know which key(s) isn't working. >>> >>> Is there any way for me to figure this out? I don't mind /getting/ the >>> message, I just want to know what's causing it. >> >> This sounds like a GnuPG error message. GnuPG would not complain about >> nonexistent keys on keyservers, but really only when a key cannot be >> imported or updated at all. >> >> Try to run the following command from the command line and see what >> GnuPG tells you: > > Looks like you're right. When I run the command from the terminal, I get > the exact same error from GnuPG. It looks like Enigmail is just spitting > out what it's getting from GnuPG. I'll hit up their mailing list. > > Thanks, > Anthony > > > > _______________________________________________ > enigmail-users mailing list > [email protected] > To unsubscribe or make changes to your subscription click here: > https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net > _______________________________________________ enigmail-users mailing list [email protected] To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
