Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 498  |
|  August Abolins to Wilfred van Velzen  |
|  not encrypted, only signed  |
|  10 Jan 20 05:39:12  |
 MSGID: 2:221/360.0 5e17f1de REPLY: 2:280/464 5e17a1a0 PID: JamNNTPd/OS2 1.3 20191227 TID: GE/2 1.2 CHRS: IBMPC 2 TZUTC: 0200 On 1/9/2020 4:52 PM, between "Wilfred van Velzen : August Abolins": WvV>>> Below is my reply to your message. It's not encrypted WvV>>> only signed (but not clearsigned). Anyone with gpg can WvV>>> decode it and view it's contents. If they have my public WvV>>> key they can verify it was me who wrote it. Why you would WvV>>> want to do it this way, I don't know. I can't think of a WvV>>> use-case for it... I will believe that when I get an -s signed message from someone for whom I do not have a key. Maybe mark will oblige, as I do not have his key. AA>> TB decrypted it automatically, (but it obscured your AA>> preface above; the decryption result in TB fills the whole AA>> reading window of the open message). WvV> I get the same thing when I decode a message with mixed WvV> content from within golded. It's to be expected. But golded WvV> doesn't decode unless told to, so I always see the mixed WvV> content first... I just discovered something interesting. TB 60 obscures the clear-text preface after auto-decrytion, but TB 2.0.0.24 (the one I am using now) shows both mixed content *with* the decrypted part. I like the way the older TB/Enigma operates! But sadly, I may have to leave TB 2.0.0.24 when my Win10 pc is ready to use. :( --- Thunderbird 2.0.0.24 (Windows/20100228) * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0) SEEN-BY: 1/123 19/10 90/1 154/10 203/0 221/0 1 6 360 227/114 229/426 SEEN-BY: 229/1014 240/5832 249/206 317 400 280/464 5003 292/854 310/31 SEEN-BY: 317/3 322/757 342/200 396/45 423/81 120 712/848 770/1 2452/250 PATH: 221/360 1 280/464 229/426 |
[ << oldest | < older | list | newer > | newest >> ]