-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 18.12.13 00:24, Philip Jackson wrote:
On 17/12/2013 14:38, Anne Wilson wrote:
On 15/12/2013 17:43, Philip Jackson wrote:
1. import public key : this seems to work and the imported key
is immediately displayed in Kleopatra but not in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15.12.13 18:43, Philip Jackson wrote:
[...]
Second Case : after the 'import public key' option has been used
and the key is available in the key manager and appears to be valid
but I have not yet set a trust level nor signed the key.
On 20/12/2013 15:48, Patrick Brunschwig wrote:
On 18.12.13 00:24, Philip Jackson wrote:
On 17/12/2013 14:38, Anne Wilson wrote:
On 15/12/2013 17:43, Philip Jackson wrote:
1. import public key : this seems to work and the imported key
is immediately displayed in Kleopatra but not in
On 17/12/2013 14:38, Anne Wilson wrote:
On 15/12/2013 17:43, Philip Jackson wrote:
1. import public key : this seems to work and the imported key is
immediately displayed in Kleopatra but not in Thunderbird key manager until
Thunderbird is restarted
This may not be entirely an Enigmail
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/12/2013 17:43, Philip Jackson wrote:
1. import public key : this seems to work and the imported key is
immediately displayed in Kleopatra but not in Thunderbird key
manager until Thunderbird is restarted
This may not be entirely an Enigmail
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hi Philip,
1. import public key : this seems to work and the imported key is
immediately displayed in Kleopatra but not in Thunderbird key manager until
Thunderbird is restarted
this is not entirely related to your situation having just
Hi all,
I thank you all (Daniel, Ludwig, Anne, Olav) for your comments on my note re:
the Details button. I'll think about some suggestions for improving the
messages given by Enigmail when the 'Details' button is solicited and then file
a bug report.
Anne - I should have added that I was using
