Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Mozilla サポートの検索

サポート詐欺に注意してください。 私たちはあなたに通話やショートメッセージの送信、個人情報の共有を求めることはありません。疑わしい行為を見つけたら「迷惑行為を報告」からご報告ください。

詳しく学ぶ
このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。
アーカイブに保管済み

Recipient's "encrypt-only" S/MIME certificate deemed not valid by Thunderbird

Roland Tanglao replied
Crack my back

My Thunderbird version at the moment is 102.13.0 (64-bit) running under Linux but the issue is not limited to either this particular version, nor the OS - colleagues running Thunderbird on Windows boxes report the same thing. We deal with an organization which issues their own S/MIME certificates. For a long time it worked flawlessly - we imported their CA as trusted, imported personal certificates of email recipients and everything worked smooth. Lately they started issuing two different certificates per person - one for signing emails, another for encryption. And now since emails from them come with a signature created with a certificate which has "Digital Signature" and "Non Repudiation" uses - everything works fine "inbound". The problem starts if we want to send encrypted emails back to them. Even if we import the encryption certificates we get (those have only "Key Encipherment" usage) and the certificates themselves are valid in any possible way (lifetime, proper CA chain imported and so on), still Thunderbird tells us it can't find proper certificate to encrypt the message.

My Thunderbird version at the moment is 102.13.0 (64-bit) running under Linux but the issue is not limited to either this particular version, nor the OS - colleagues running Thunderbird on Windows boxes report the same thing. We deal with an organization which issues their own S/MIME certificates. For a long time it worked flawlessly - we imported their CA as trusted, imported personal certificates of email recipients and everything worked smooth. Lately they started issuing two different certificates per person - one for signing emails, another for encryption. And now since emails from them come with a signature created with a certificate which has "Digital Signature" and "Non Repudiation" uses - everything works fine "inbound". The problem starts if we want to send encrypted emails back to them. Even if we import the encryption certificates we get (those have only "Key Encipherment" usage) and the certificates themselves are valid in any possible way (lifetime, proper CA chain imported and so on), still Thunderbird tells us it can't find proper certificate to encrypt the message.

すべての返信 (1)

Hi "Crack my back" Perhaps the folks at #openpgp:mozilla.org on Matrix can help

Cheers! ...Roland