-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 1/27/2020 2:21 PM, between "Tommi Koivula : August Abolins":

t> Also the combination "JamNNTPd + UTF-8" may be the reason...
t> ---

That one of yours arrived as Content-Type: text/plain;
charset=ISO-8859-1, (non-utf8), and decoded fine, on both TB68 and
TB24/Enigma as well.

The only messages that fail originate from TB68/Enigmail when using
utf-8 in this echo.

I doubt that JamNNTPd has anything to do with munging the messages
because it is happening in email originating from the TB68 system too!
:(   A recent email that I accidentally sent as text/plain;
charset=windows-1252, failed too.

Maybe the default "View incoming as" and "Write outgoing as" settings
may be doing some overrides?  Or.. would the fonts that I use to VIEW
have something to do with it?

On the other hand, outbound signed clear-text iso-8859-1 from the TB24
(this message) is behaving nicely in this echo and email.

This seems to be a weakness in the signed clear-text process when one is
not mindful of the charset that is in use.


-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE0OsqKVIE8xZ+slA87w6JZVeJWJsFAl4veM4ACgkQ7w6JZVeJ
WJt9wwf9Fp8aGcKMt6f+Vos12+NHo1h2PY5EMuquetCz6st1wbOH0nE1bMSVNCFc
QhQaW0IJkKZayeHaF9ne1JnYoDMHY3FGfw79Paz+tbancaXeaUSR38YxXX3R4tdT
YUmZv8+W/vqa9vTfUjzvo5Q6SpjU4BKMkTq3lgkrF3NQIInzNTUxdtik1enBlu6p
dSx1iucqv0ZFgRMN0dK5ABLTSrOLPlEutvAgjXTR1DsR4eK5J1RifNhTBMl5C36d
6pMJYgLBHZrVIM4taifFaWId0e1ayJs6kOFhDcU4MNL0m5JEt6s9iCrrfZFjvnXB
GyWDTWHPodbYVqlY07VZ8En7icl3+A==
=GDMW
-----END PGP SIGNATURE-----

--- Thunderbird 2.0.0.24 (Windows/20100228)