Hi August,

On 2020-01-25 18:46:39, you wrote to mark lewis:

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

 AA> On 07/01/2020 8:10 a.m., mark lewis : August Abolins wrote:

 ml>> encrypted and/or signed messsges are allowed in this echo...
 ml>> AFAIK, this is the only echo that allows such

 AA> I recently updated my Win7 pc to TB 68 + the corresponding
 AA> Enigmail/GPG plugin.

 AA> But signed clear-text email seems to be rolling out with:

 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


 AA> Signed clear-text messages from other people in this echo look good
 AA> and process properly.

 AA> So, I am testing one originating from this new TB68/Enigmail combo to
 AA> see if the "invalid armor header" is a problem here.

 AA> I'd hate to roll back TB.  But maybe all I have to do is rollback the
 AA> Enigmail plugin version?


 AA> - --
 AA> Quoted with Reformator/Quoter. Info = https://tinyurl.com/sxnhuxc
 AA> -----BEGIN PGP SIGNATURE-----

 AA> iQEzBAEBCAAdFiEE0OsqKVIE8xZ+slA87w6JZVeJWJsFAl4scOIACgkQ7w6JZVeJ
 AA> WJugNQf/TcvM1zQJi8hN42CQDCtsTbX0hu2B/Smg3k/zy6aCB5FabIRGxgQCt3C0
 AA> yROmIvUpLLwQQ8MMwzYqQfvb25ifmt1NwCNHl2sPSQVeIUQPaU/6PNeikgSNhmXH
 AA> w7SxK7upP17sAjIY3sG+lOto2S6HgDtt8MVyZrbr4BAUK6EfG475oTsKgo3jezTc
 AA> ALa2W3tVByYS6TlnvuyqEFJkbShw6ddl+lIclYsK3A8B0y4S+rOLlklUyloUbVY1
 AA> u4BBpQAyWXzwLb9Mfm7W/X0pcCzlxCEtn4RXblMg9o7UnVNviYupc31HbLCAo/FO
 AA> 61EYIA3M6lOe/QCfx6jk62qF+xFNLg==
 AA> =iByN
 AA> -----END PGP SIGNATURE-----

I'm getting:

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

On this one...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815