Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 380  |
|  Wilfred van Velzen to August Abolins  |
|  Re: scrap key for ID 5789589B  |
|  05 Jan 20 13:03:31  |
 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 5e11d0db REPLY: 2:221/360.0 5e112e08 Hi August, On 2020-01-05 02:30:00, you wrote to me: AA> Apparently, I haven't fully explored its full configuration options. AA> There are so many. I saw a setting on my other pc where I could AA> "assign" other identities to the existing ones. Maybe that is the AA> answer. Probably! AA> Next to being able to sign messages in echomail/newsgroups, fully AA> encrypted messages only make sense in email - direct to a specific AA> individual. Or routed netmail! WvV>> But are those older keys still usable? I have two keys from WvV>> 1993, I no longer remember the passwords for. :-( But they WvV>> aren't on the keyservers afaik, so nobody will be tempted WvV>> to use them. ;) AA> That's the beauty of pulling down the keys and checking their AA> properties. The properties will reveal creation dates, expiry dates, AA> revocations,etc. It would be relatively easy to just pick the most AA> recent date, and send a brief hello message with a CC: and see which AA> ones reach their target. If there are multiple keys to choose from... 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 |
[ << oldest | < older | list | newer > | newest >> ]