TID: FMail-lnx64 2.1.0.18-B20170815
RFC-X-No-Archive: Yes
TZUTC: 0200
CHRS: UTF-8 2
PID: GED+LNX 1.1.5-b20161221
MSGID: 2:280/464 5ef716df
REPLY: 2:221/1.58@fidonet e5cc8f78
Hi August,

On 2020-06-26 18:08:00, you wrote to All:

 AA> I see this when I look up my keys:

 AA> pub  2048R/5789589B 2020-01-02

 AA> Fingerprint=D0EB 2A29 5204 F316 7EB2  503C EF0E 8965 5789 589B



 AA> uid August Abolins 

 AA> sig  sig3  5789589B 2020-01-06 __ 2024-12-31 [selfsig]



 AA> uid August Abolins 

 AA> sig  sig3  5789589B 2020-01-02 __ 2024-12-31 [selfsig]

 AA> sig  sig2  56CDF35B 2020-01-03 __ __ Tommi Koivula 

 AA> sig  sig3  2A6F822A 2020-01-03 __ __ Tommi Koivula 

Hmm, double spacing on the inserted part?

 AA> Does that mean that Tommi signed my key?

Looks like it.

 AA> If so, I should probably have a copy of Tommi's public key submission.

I think you already do, because otherwise it wouldn't have shown Tommi's name
and email adres, but something like [unknown], I think.

 AA> Is this simply accomplished with a refresh from a server?

 AA> I tried:

 C:\>> gpg --refresh-keys --keyserver pgp.key-server.io
 AA> gpg: refreshing 12 keys from hkp://pgp.key-server.io
 AA> gpg: keyserver refresh failed: No keyserver available

Try:

# gpg --keyserver hkp://pool.sks-keyservers.net --keyserver-options
no-honor-keyserver-url --refresh-keys koivula

Or replace the --refresh-keys with --recv-keys, to get/update all Tommi's keys
from the key server...

 AA> But.. I *can* visit the server and search via the web interface, no
 AA> problem.

Maybe it doesn't use the hkp: but http: protocol?

 AA> What servers is everybody else using that prove to be more reliable?

I don't use them very often, so I wouldn't know about reliability...

 AA> If, I can't use the refresh function, do I just delete my local copies
 AA> of Tommi's keys, and just look for newer ones of his 56CDF35B and
 AA> 2A6F822A?

You don't have to delete them first, to import an updated version...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
 * Origin: FMail development HQ (2:280/464)
SEEN-BY: 1/123 90/1 120/340 601 123/131 226/30 227/114 702 229/101
SEEN-BY: 229/424 426 664 1014 240/5832 249/206 317 400 292/854 317/3
SEEN-BY: 322/757 342/200
PATH: 280/464 229/101 426