Hi August,
On 2020-01-25 19:25:44, you wrote to All:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Testing updated TB68+Enigmail/GPG plugin here with signed clear-text.
In outbound email, TB/Enigmail seems to be generating an rogue "Â" as
per below.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Â
Now I reply..  from new TB at Win7pc.
On 25/01/2020 10:39 a.m., August A wrote:
Let's see how this looks.
-----BEGIN PGP SIGNATURE-----
Â
iQEzBAEBCAAdFiEE0OsqKVIE8xZ+slA87w6JZVeJWJsFAl4sYWMACgkQ7w6JZVeJ
WJskHAf9GQAJ4FtsHpCOgXGeZxzF56/B/7rSUQ1TAerAsgvcrdDKz/4zOXh5UeEu
UwsLQ3jTLTmZJftBPx58JP/LTBlc2q5gBGuOu46FkbaFngrm/ubG4vgCNQ2DbfOU
C+NJjx26R7TS+Vr9HZn5xdLEGczlRk6Wz0I8QHFLUp/cqMEgUiuiSSFoYB5UbCWX
2QN3A5OB4rLJm9+h9jk0Zj0FVrnqYJSqSIUEsGFK4y4BO198q2ZA95wj4pa9ZgcL
j4BHPd5v7/ZLezB3UFBeDxt+/uUq+8vCwiUOrDdxhrLyy76yrd8ahx6QUChORhHu
EWwXTE6ZTw9zMqPHiqtrtDdXWtbR2g==
=7pgO
-----END PGP SIGNATURE-----
Just checking to see if the same thing happens in echomail, and if
anyone else sees it.
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEE0OsqKVIE8xZ+slA87w6JZVeJWJsFAl4segoACgkQ7w6JZVeJ WJvyAggApGCoTf177EUQk58ziuUlMxiTvAF81uai8D/TACaGlmupZaUMeKHS87d6 Hi++67aKAzEAHthwl8asG9MmrYBfKurIKw0pjQNHwUh1mClkNex0JzFu76WNDWZf Vx+T7Y3j20BnKeciPua32zNi03s6Fgu1tNgfSDE/kakHtCwtNQS4wgCT/rq10pOJ TU76e+nUKd2BSuU1HwqJWNq6FxYMbO8z2BAUj4rFW3K83ldqkZMA7GzvD7c7WeKN I9PvGGRcR8LzpcbF5Zz7xuDi0it4mBnwbcyNYILyXEbAUdRXeuSfAo9bV4l2xsS5 aog6gLbCwHmglPBtKE4ssdwgJN0v2Q==
=K1p+
-----END PGP SIGNATURE-----
The outer signature verifies ok.
If I de-indent the the inner message and try to verify it, I get:
¶\n
gpg: invalid armor header:
¶\n
gpg: invalid armor header:
It looks like some utf character(s), maybe the BOM ?
Bye, Wilfred.
--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)