MSGID: 2:221/360.0 5e179ca2
REPLY: 2:280/464 5e17965d
PID: JamNNTPd/OS2 1.3 20191227
TID: GE/2 1.2
CHRS: UTF-8 2
TZUTC: 0200
On 09/01/2020 4:08 p.m., Wilfred van Velzen : August Abolins wrote:

> Below is my reply to your message. It's not encrypted only signed (but
> not clearsigned). Anyone with gpg can decode it and view it's contents.
> If they have my public key they can verify it was me who wrote it. Why
> you would want to do it this way, I don't know. I can't think of a
> use-case for it...

TB decrypted it automatically, (but it obscured your preface above; the
decryption result in TB fills the whole reading window of the open message).

It contained this security header info:

Part of the message signed Good signature from Wilfred van Velzen
 Key ID: 0xD50ECD4F514B75DC0A064F893BB37DA84A97932B
/ Signed on: 01/09/20, 3:58 PM Key fingerprint: D50E CD4F 514B 75DC 0A06
4F89 3BB3 7DA8 4A97 932B Used Algorithms: RSA and SHA-1

I assume that it can then be read by anyone who has the key of the
author.  ?

If so, then a good practical use would be if you wanted a totally
obscured message stream by adding an extra layer of frustration to just
anyone, or even from the bots that skim messages. ?  I kinda like that.

It would force the would-be reader to collect the keys of everyone who
is writing the messages, but still remain a lurker. ?

Not good good for sharing sensitive info though.

--- Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 
hunderbird/60.9.1
 * 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