When receiving signed but not encrypted messages, thunderbird complains with "invalid digital signature" and "technical error deteced". Unpacking the message and checking… (Lesen Sie mehr)
When receiving signed but not encrypted messages, thunderbird complains with "invalid digital signature" and "technical error deteced". Unpacking the message and checking with gpg manualy verifies the signature correctly. Messages encrypted and signed are verified correctly.
When looking at the logs in the console, I can see:
<< ----
openpgp: Parsed contentTypeLine: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------95ynGFLP1eI6rMalg5HH0Iop" mimeVerify.sys.mjs:133:14
openpgp: Decrypting message: -----BEGIN PGP SIGNATURE-----
..[snipped]
END PGP SIGNATURE-----
decryption.sys.mjs:143:14
openpgp: Nothing to decrypt/verify. decryption.sys.mjs:176:16
openpgp: Decrypting message: -----BEGIN PGP SIGNATURE-----
..[snipped]
END PGP SIGNATURE-----
decryption.sys.mjs:143:14
openpgp: Nothing to decrypt/verify. decryption.sys.mjs:176:16
openpgp: Parsed contentTypeLine: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------95ynGFLP1eI6rMalg5HH0Iop" mimeVerify.sys.mjs:133:14
openpgp: Found signed MIME message; micalg=pgp-sha256 mimeVerify.sys.mjs:148:16
openpgp: Parsed contentTypeLine: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------95ynGFLP1eI6rMalg5HH0Iop" mimeVerify.sys.mjs:133:14
openpgp: Found signed MIME message; micalg=pgp-sha256
>>----
Does simply singing without encryption require some special settings?