1 |
On Friday 20 Jan 2012 07:57:38 Frank Steinmetzger wrote: |
2 |
> On Thu, Jan 19, 2012 at 01:22:50PM -0600, Paul Hartman wrote: |
3 |
> > On 1/19/2012 11:32 AM, Chris Walters wrote: |
4 |
> > > On 1/19/2012 11:57 AM, Frank Steinmetzger wrote: |
5 |
> > >> On Thu, Jan 19, 2012 at 12:53:07AM -0600, Dale wrote: |
6 |
> > >>> While on this subject, sort of. Who on here as their email set up to |
7 |
> > >>> encrypt and decrypt emails? I want to test some things OFF LIST. |
8 |
> > >> |
9 |
> > >> Well, if you had signed your mail, then I could write you encrypted. |
10 |
> > >> :) |
11 |
> > > |
12 |
> > > This is a test. Enigmail has been trying to use a revoked and expired |
13 |
> > > key to sign my messages, lately. |
14 |
> > > |
15 |
> > > Chris |
16 |
> > |
17 |
> > Looks good to me, at least based on what's presently available in the |
18 |
> > keyservers. |
19 |
> |
20 |
> Hm... I seem to be too dumb. Mutt tells me that the msg is signed, but |
21 |
> doesn't tell me by whom (I know that I need to have the public key in my |
22 |
> keyring to see a name, but it doesn't even tell me the key ID). Saving the |
23 |
> whole mail to a file and verifying the sig doesn't work either, that too |
24 |
> is obvious because 1) only the text is signed, not the rest of the mail |
25 |
> and b) the signed stuff and the sig need to be two different files for gpg |
26 |
> --verify to work. So I saved the signature.asc and the text separately. |
27 |
> Now verification works and I see a key ID, but using gpg --search <key ID> |
28 |
> doesn't find the given key on the server. |
29 |
> |
30 |
> GPGing was much easier when KMail still worked. ^^ |
31 |
|
32 |
Yes, I dabbled with mutt but I found the gpg and s/mime rather cranky compared |
33 |
with the super-smooth integration of kmail and kgpg. Unfortunately with |
34 |
kdepim-4.7 the whole kmail experience has been a rather unpleasant one for me. |
35 |
:( |
36 |
-- |
37 |
Regards, |
38 |
Mick |