TID: FMail-lnx64 2.1.0.18-B20170815
RFC-X-No-Archive: Yes
TZUTC: 0100
CHRS: UTF-8 2
PID: GED+LNX 1.1.5-b20161221
MSGID: 2:280/464 5e0fc340
REPLY: 2:221/360 5e0fb622
Hi Tommi,

On 2020-01-03 23:45:16, you wrote to me:

 WV>> gpg: WARNING: This key has been revoked by its owner!
 WV>> gpg:          This could mean that the signature is forged.
 WV>> gpg: reason for revocation: No reason specified
 WV>> gpg: WARNING: This key is not certified with a trusted signature!
 WV>> gpg:          There is no indication that the signature belongs to the
 WV>> owner.
 WV>> Primary key fingerprint: 4944 C463 71C6 4E3E 6077  422B 36A7 031E 56CD
 WV>> F35B

 WV>> ... on this message. So you are using a revoked key!?

 TK> Interesting.. Why is GPG using the revoked one, when there is a working
one
 TK>  available... Hmm...

I don't know. Maybe it's the default? (Can you set a default key?)

This one had a valid signature from a valid key.

 TK>>> I just signed the key of August. :)

 WV>> And where is it? If it's only in your keyring, it's not very usefull
 WV>> for the rest of
 WV>> the world, that you signed it. ;)

 TK> It should have been uploaded to the keyserver.

Of course! Got it... ;)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
 * Origin: FMail development HQ (2:280/464)
SEEN-BY: 1/123 90/1 154/10 203/0 221/0 227/114 229/426 1014 240/5832
SEEN-BY: 249/206 317 400 280/464 5003 292/854 310/31 317/3 322/757
SEEN-BY: 342/200 396/45 423/120 712/848 770/1 2452/250
PATH: 280/464 229/426