Hello!
I just observed a new issue with S/MIME. When trying to send an encrypted mail to somebody new, I get an error “End-to-end encryption requires resolving certifica… (jàng ci lu gën a bari)
Hello!
I just observed a new issue with S/MIME. When trying to send an encrypted mail to somebody new, I get an error “End-to-end encryption requires resolving certificate issues with somebody@example.com”.
The message is not very helpful, and doesn’t propose any solution. So a web search gave me this article: Prerequisite for sending an encrypted email message. It states:
> If Thunderbird considers the email's signature and the sender's certificate valid, it will automatically be imported and available when you attempt to encrypt an email to that correspondent using the S/MIME technology.
When I open the sender’s mail, the signature is confirmed as valid by Thunderbird.
Ignoring the warning message and trying to send the encrypted mail results in the following error in the log:
`mailnews.send: NS_ERROR_ILLEGAL_VALUE: Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIMsgComposeSecure.beginCryptoEncapsulation]`
So, I verified in my list of certificates for people, and that new person didn’t figure in the list. Other people did, the last one from 6 June.
Is it possible there’s a bug causing TB to not import the certificate when I open the mail?
What would a workaround be? Is there a way to import a sender’s certificate manually from their signed mail?