Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 600  |
|  Wilfred van Velzen to August Abolins  |
|  Re: updating keys..  |
|  28 Jun 20 12:35:32  |
 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 5ef872de REPLY: 2:221/1.58@fidonet e5d4997d Hi August, On 2020-06-27 22:43:00, you wrote to me: AA>> The report above is what I see at pgp.key-server.io AA>> Locally, I get this: AA> (Whooops.. apparently I sent out a partially written reply!) Indeed you did. ;) AA>>>> But.. I *can* visit the server and search via the web interface, no AA>>>> problem. WvV>>> Maybe it doesn't use the hkp: but http: protocol? AA> I tried both. Same result. It seems the problem is limited to my XP AA> machine (mobile ISP). But accessing the servers from command line works AA> fine from my Win7 pc (DSL). Strange... AA>>>> If, I can't use the refresh function, do I just delete my local AA>>>> copies of Tommi's keys, and just look for newer ones of his AA>>>> 56CDF35B and 2A6F822A? WvV>>> You don't have to delete them first, to import an updated WvV>>> version... AA> But.. if I can't update the keys from a server, I have to do it AA> manually. That is, I would have to export my keys from the Win7 pc, AA> and carry them over to my XP pc. Bummer. Where you can just import them. You don't have to delete them at the destination first. If they already exist they are updated with the import... 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 |
[ << oldest | < older | list | newer > | newest >> ]