You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
after upload of key 6E0A 4E90 3241 34F0 2788 445D 044A 25F5 267D C236 the keyserver threw an error message that went something like "email could not be sent", reducing the key via gpg --armor --export-options export-minimal --export 6E0A4E90324134F02788445D044A25F5267DC236 resolved the issue.
My best guess would be that the issue is due to the attached photo user id, but it might be something else as reproduction with a random other key with photo id failed.
Sorry for vague error report. I will put better details when I set up my own mailvelope keyserver. But maybe this already helps to find the issue?
Sincerely,
Malte
The text was updated successfully, but these errors were encountered:
I just tried this on my own server (blocked email from being sent), the upload seemed to work fine. I used the pubkey from https://keybase.io/fabionatali (which is for 6E0A4E90324134F02788445D044A25F5267DC236 you mention). Maybe you should try again? :)
btw, if I try to upload it to keys.mailvelope.com , then it says key already exists. Meaning it was uploaded successfully and the email was acknowledged by the owner.
So...another invalid issue, looks like.
Hi,
after upload of key
6E0A 4E90 3241 34F0 2788 445D 044A 25F5 267D C236
the keyserver threw an error message that went something like "email could not be sent", reducing the key viagpg --armor --export-options export-minimal --export 6E0A4E90324134F02788445D044A25F5267DC236
resolved the issue.My best guess would be that the issue is due to the attached photo user id, but it might be something else as reproduction with a random other key with photo id failed.
Sorry for vague error report. I will put better details when I set up my own mailvelope keyserver. But maybe this already helps to find the issue?
Sincerely,
Malte
The text was updated successfully, but these errors were encountered: