MSGID: 2:221/360.0 5e2f5928
REPLY: 2:221/360.8110 5e2f383a
PID: JamNNTPd/OS2 1.3 20191227
TID: GE/2 1.2
CHRS: UTF-8 2
TZUTC: 0200
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 27/01/2020 2:21 p.m., Tommi Koivula : August Abolins wrote:


a>> Thank you.  Looks like clear-signed messages MUST be posted in
a>> plain ASCII only.  Or, at least that is the situation with
a>> TB/Enigmail.

t> Also the combination "JamNNTPd + UTF-8" may be the reason...
t> Origin: nntp point (2:221/360.8110)


Yours with utf-8 decoded fine:

	Enigmail Security Info
	Part of the message signed
	Good signature from Tommi Koivula 

(I still have to see how TB24 at my other pc handles it.)

But you're adding new variables with the way you are processing the
point source.  At least you have a clean option.

OK, this one going back to you with utf-8 from my TB/Enigmail combo.

It will probably fail.
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE0OsqKVIE8xZ+slA87w6JZVeJWJsFAl4vWSgACgkQ7w6JZVeJ
WJujywgA0eT3S7TlMPbmYBoUoPcNasPeG4vm8vgTzmRh6ga8DzEdEH80yj83uELw
Vo4wC9UMyFw++V+ViEeo3bhq3NvEtVH1eCA0fPO4OZ5ZtGg8N8mRXQLbSGMtO82n
NACs3ZUt7Yg6W2VE7JXGNOe9y1EFgSqsLf8Jt9mA8uozXez05WX8GwY/YgbBJEqB
eUaLt8qY+UmP70eg7H0cPWtkxK3deQHVU56pEVsXGK9wmDhbvP/nL8KWOMh9y1ji
BWbOEHm8esEVr6mR/7qK9U/ij+pZ5773SmFD0zQiNsNfKBvrqlpf0Cu2khh4Ssp9
qkyUkXhB+5ykkaIxh7belr8x5KgEGg==
=Mgin
-----END PGP SIGNATURE-----

--- Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) Gecko/20100101 
hunderbird/68.4.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 288/100 292/854
SEEN-BY: 310/31 317/3 322/757 342/200 396/45 423/81 120 712/848 770/1
SEEN-BY: 2452/250
PATH: 221/360 1 280/464 229/426