| 1 |
Hey there! |
| 2 |
|
| 3 |
I wonder why Kmail does not import any gpg keys. For example on this list, |
| 4 |
many people sign their messages. But Kmail tells me something like this: |
| 5 |
|
| 6 |
> Message was signed on xxx with unknown key xxx. |
| 7 |
> The validity of the signature cannot be verified. |
| 8 |
> Status: No public key to verify the signature |
| 9 |
|
| 10 |
OpenPGP is selected in "Crypto Backends" with default keyserver |
| 11 |
http://pgp.mit.edu |
| 12 |
Automatically import keys and certificates is also selected. |
| 13 |
|
| 14 |
gpg-agent is running, with the following config (gpg.conf): |
| 15 |
|
| 16 |
> grep -v '^#' ~/.gnupg/gpg.conf | uniq |
| 17 |
|
| 18 |
> keyserver-options auto-key-retrieve |
| 19 |
> |
| 20 |
> use-agent |
| 21 |
|
| 22 |
> default-key 40A7BD65 |
| 23 |
|
| 24 |
> utf8-strings |
| 25 |
> verbose |
| 26 |
> utf8-strings |
| 27 |
|
| 28 |
> encrypt-to 0x40A7BD65 |
| 29 |
|
| 30 |
and gpg-agent.conf: |
| 31 |
|
| 32 |
> grep -v '^#' ~/.gnupg/gpg-agent.conf | uniq |
| 33 |
> pinentry-program /usr/bin/pinentry-qt |
| 34 |
> no-grab |
| 35 |
> default-cache-ttl 1800 |
| 36 |
> |
| 37 |
> debug-level basic |
| 38 |
> log-file socket:///home/pholthau/.gnupg/log-socket |
| 39 |
> allow-mark-trusted |
| 40 |
|
| 41 |
I am running Kmail 1.9.7 (KDE 3.5.8) and gnupg 2.0.7. |
| 42 |
|
| 43 |
Anyone knows whats going wrong? |
| 44 |
|
| 45 |
|
| 46 |
Thanks |
| 47 |
Patrick |
Archives