Camel: Set proper S/MIME signature verification status
I'm using both, PGP and S/MIME.
With PGP, a newly imported public key of some person is not trusted by default. When receiving a signed email from the person with this public key, evolution shows a yellow bar with "Valid signature, but sender could not be verified (NAME, <EMAIL>)".
With S/MIME, a user certificate is not trusted by default (evolution settings - certificates). When receiving a signed mail from a person with this certificate, evolution shows a red bar with "Invalid signature (NAME, <EMAIL>)", even though the signature is perfectly valid (checked with OpenSSL). When expanding the bar, evolution prints the root cause with ~"signature certificate is not trusted".
- This seems like inconsistent behaviour between PGP and S/MIME
- For S/MIME: It seems wrong to me to display "invalid signature", even though the signature is valid (checked with OpenSSL)
- For S/MIME: It would be more helpful to also show a yellow bar with something like "Valid signature, but sender certificate is not trusted (NAME, <EMAIL>)", similar to what is displayed with PGP.
Edited by Roy Meissner