On Fri, Jun 11, 2010 at 06:59:23PM +0000, Camaleón wrote: > On Fri, 11 Jun 2010 21:37:57 +0300, Alexander Batischev wrote: > > > On Fri, Jun 11, 2010 at 06:21:14PM +0000, Camale??n wrote: > > >> In order to verify a signed message, either you have to previosuly > >> import the key into your keyring or you need to setup Mutt to retrieve > >> the key from public servers. > > > > I have all the keys retrieved (previously, I run gpg --recv-keys keyID > > every time I face with new key; now I just set "keyserver-options > > auto-key-retrieve" in ~/.gnupg/gpg.conf, so all new keys are retrieved > > automatically). And it still doesn't explain why my own signature can't > > be verified, too. > > Then maybe is that you have to "explicitely" import the key and trust > that key. Did you already do that? :-?
Well, okay, I set trust for my key to 5 (absolute) and for Boyd's to 4. Now when I open my message, I see the following: [-- PGP output follows (current time: Fri Jun 11 23:59:09 2010) --] gpg: Signature made Fri Jun 11 21:37:57 2010 EEST using DSA key ID 69093C81 gpg: Good signature from "Alexander Batischev <eual...@gmail.com>" [-- End of PGP output --] Better than before, but mutt still claims "signature can NOT be verified"… > Also, test it with another e-mail client (thunderbird, kmail, > evolution...) so you can compare the results. One thing why I don't like GUI apps as much as CLI: something might work or might not, and in both cases you hardly find out why. Are there another mail client as flexible in setup as mutt, so if I see GPG working in there I could look how it is configured? -- Regards, Alexander Batischev 1024D/69093C81 F870 A381 B5F5 D2A1 1B35 4D63 A1A7 1C77 6909 3C81
signature.asc
Description: Digital signature
