MSGID: 2:221/360.0 5e2c70e6
REPLY: 118.fido-publicke@1:3634/12 2279b9a9
PID: JamNNTPd/OS2 1.3 20191227
TID: GE/2 1.2
CHRS: UTF-8 2
TZUTC: 0200
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

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

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

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

	gpg command line and output:
	C:\Program Files\gnupg\bin\gpg.exe
	gpg: invalid armor header: Â \r\n
	gpg: invalid armor header: Â \r\n


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

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

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


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

iQEzBAEBCAAdFiEE0OsqKVIE8xZ+slA87w6JZVeJWJsFAl4scOIACgkQ7w6JZVeJ
WJugNQf/TcvM1zQJi8hN42CQDCtsTbX0hu2B/Smg3k/zy6aCB5FabIRGxgQCt3C0
yROmIvUpLLwQQ8MMwzYqQfvb25ifmt1NwCNHl2sPSQVeIUQPaU/6PNeikgSNhmXH
w7SxK7upP17sAjIY3sG+lOto2S6HgDtt8MVyZrbr4BAUK6EfG475oTsKgo3jezTc
ALa2W3tVByYS6TlnvuyqEFJkbShw6ddl+lIclYsK3A8B0y4S+rOLlklUyloUbVY1
u4BBpQAyWXzwLb9Mfm7W/X0pcCzlxCEtn4RXblMg9o7UnVNviYupc31HbLCAo/FO
61EYIA3M6lOe/QCfx6jk62qF+xFNLg==
=iByN
-----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