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

On 1/25/2020 3:42 PM, between "Wilfred van Velzen : August Abolins":

AA> I recently updated my Win7 pc to TB 68 + the corresponding
AA> Enigmail/GPG plugin.
AA>
AA> But signed clear-text email seems to be rolling out with:
AA>
AA>   gpg command line and output:
AA>   C:\Program Files\gnupg\bin\gpg.exe
AA>   gpg: invalid armor header: Â \r\n
AA>   gpg: invalid armor header: Â \r\n

WvV> I'm getting:

WvV> gpg: Signature made za 25 jan 2020 17:46:26 CET using RSA key ID
5789589B
WvV> gpg: BAD signature from "August Abolins " [unknown]

WvV> On this one...

THANK YOU.

Something is wrong with TB 68 + Enigmail.   I am guessing it might have
to do with using UTF-8 for message encoding with that system.

The invalid "Â" char in the PGP block is suspect of that cause.

- From my quick initial research, there is supposed to be the equivalent
of a   where the "Â" shows up in the block.

Meanwhile, this time, THIS message is originating from the TB 20.0.0.4.
 I am using UTF-8 message encoding, like I have configured for these
nntp message areas here.

Let's see how the signed clear-text behaves.


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

iQEzBAEBCAAdFiEE0OsqKVIE8xZ+slA87w6JZVeJWJsFAl4s+E8ACgkQ7w6JZVeJ
WJts8wgApfinpTTIUpnag4dTVFFXRo21CW847SRm/xuNCWbvBRaxLTxDhf3gV5wo
RsiRMCTx1hoFYaS1ZpWg0ZixcbasHvAfz5OBX3wN8is9NW94lxaQOhUYxoi2vZ9C
dvN10bvTWoorWfCYt7kkbdFfVkJynEb8vO2HfCBcy6XxRz+a4BNgqs3qNPs36Juv
YN/w8qlWYFPEOr0HuLCulpHBqDvPT1r/aS7yK7MIE6B2v36GPYT4DxKQGNyQP3HE
GziAzVlzJVumt5HpLT9wjgPdn6VvOTPM4EPkxLcN0z1fsZHY/h5RhkcgrAFnRUhp
qfD2gJI4TomJY03c7aTc8/3wMiFUug==
=VfXg
-----END PGP SIGNATURE-----

--- Thunderbird 2.0.0.24 (Windows/20100228)