-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Hi Lupa, > Is my first message here Welcome! According reporting quality: Please first state what the situation was before (incl. OS, versions, etc.), what you did, what you expected to happen and what did (not) work. > *A. Empty keyring* > 1. Today I tried to send an email but got private key > error: > "Can't find your key in keychain" (something like this) > 2. So I opened my Enigmail keychain and realized that it's empty. > All keys gone included my private key. > 3. Then, I found some dirmngr errors in syslog: > resolving 'pgp.mit.edu' failed: Connection closed in DNS > can't connect to 'pgp.mit.edu': host not found > error connecting to 'https://pgp.mit.edu:443': Conn. closed in DNS > command 'KS_GET' failed: Connection closed in DNS > error accessing 'http://pgp.mit.edu:11371/pks/lookup?op=get&; > options=mr&search=0x<REMOVEDKEYID>': http status 502 > It seems that I can't connect to pgp.mit Yes. But it's not an enigmail but a dirmngr (part of GnuPG) issue. > It seems that Enigmail deleted the keys? Probably not, Enigmail will only > instruct GnuPG to delete keys if you explicitely consent to. More likely your keyring was corrupted by other means or that you did not set it up correctly in the first place. Or Enigmail was set to usi a different path / GPG home. But you DO have a proper backup of your keyring, don't you?! > I did not delete a folder or changed settings at all. Well, that's what > everybody says, right? ;-) Sorry ... > Thunderbird version: 60.6.1 (updated from 60.5.1 in 3/29/2019) > Enigmail > version: 2.0.10, GnuPG version: 2.2.4-1ubuntu1.2 OK, "1ubuntu1.2" means you're on Ubuntu. Which Ubuntu flavor/version? Does "updated" mean that you did have a working TB+EM+GPG config incl. private keys that you could sign/decrypt with? What DID change? Did you do a system software update (including TB)? Was EM installed manually from our website or as package? Did you try to create a debug trace yet? Please see https://enigmail.net/index.php/en/faq?view=topic&id=15#faqLink_6 - -> click/open "How can I create a debugging log file" > *B. Documentation error* > When I clicked "report a defect" then "Create an > execution trace", > the link sent me to FAQ's "Usage", but no "execution trace" there. No, documentation works as is should (see above). But you need JavaScript enabled to "open" the 2nd FAQ link there. It then reads: In order to support our users, and especially for fixing defects, we often require a debug log file. Enigmail contains a function that creates such a log file if needed. - - Open the Enigmail Preferences panel (menu Enigmail -> Preferences) - - Activate the checkbox Display Expert Options and close the dialog - - Open the menu Enigmail > Debugging Options > View Log. - - Click the Save Log to File ... button to save the log. Olav -----BEGIN PGP SIGNATURE----- iQGzBAEBCAAdFiEELI5D2uuyOz5mivRZoZffa2rh71YFAlytD0cACgkQoZffa2rh 71aHwgv9HtUUoJktBbZrk1jKnavP8IOrtoBJD9hlTCmUOYuuatqDgysX6EYMErsc tBgGQ/aGfy6UhU4/VHxkR3lTDc7dzEDDEOOqJiUVvYvUQ9w3sajdl7Doa4YPGUp8 rmHpm+Li/3KIbGkiLohe5LyxTdlVft5fzo+iycp91LlBv0jkLaZHtOH+yo+au34A 66W42hxhUUFlJ8nhbBY3qZjEPjWWiK3flaIDq7NWUB+S32FY70+ge08mvx3l5SbL DodnvvbLdoATOAr/oKw3YHH/sz8+eXKYrl/LJ0S3cBcX29omz05l49xegsiEavqG zR656pbOdNtoQC04ummKp2miHws6UGAp0ZwuFn8KC3kXRj8oO7w/2I03+e48f9Hx /Yx6MKMcDlcvNAPAqhtm3TR3wEXysaFHtc2l3PGhxG9kFpZswKCnmcNLYLct8lwY zMYrdx1+MtefcPcoOjGVJnUzE0/RyLiiTf3kElPZmOR8qWfy7yRWtGsmpo7PIaiN AAJkm8bc =RJav -----END PGP SIGNATURE-----
_______________________________________________ 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
