gnupg/dirmngr does not surface 429 and other unexpected error code responses from keyserver
Which of our tools is giving you problems?
gnupg/dirmngr/gpg keychain
Attach a screenshot of the version info for all installed components (how to: https://gpgtools.tenderapp.com/kb/faq/where-can-i-find-version-info...):
Nightly 3604n
Describe your problem. Add as much detail as possible.
I recently got blocked/rate limited by a keyserver that began returning "Error code: 429 Too Many Requests" to all my requests. I didn't realize this for some time though because keyserver commands sent via gpg CLI and GPG Keychain were responding "No keys found" and not surfacing the error to let me know the query had been blocked. I have confirmed the same behavior for other error codes as well, such as internal server errors in the 5xx range.
What did you expect instead
I would expect the error code would be surfaced so the user is aware the command failed and not believe it successfully queried a keyserver and found no keys for the query. Likely it would be easiest to look for the "expected" errors codes like 200 (and maybe 301/302 redirects if gpg can follow those?) and 404 for not found and surface others as errors vs. having to keep up with the full (and possibly changing) list of all "error" codes
Describe steps leading to the problem.
Get blocked/rate limited by a keyserver to the point it responds with Error code: 429 Too Many Requests for all queries & then attempt to perform a keyserver action such as --search or --recv-keys
Are you using any other Mail.app plugins?
n/a
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac