搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Thunderbird v78.6.0 (windows, 32bit): unable to send GPG encrypted emails

  • 1 回覆
  • 1 有這個問題
  • 1 次檢視
  • 最近回覆由 mpelzer

more options

Hello,

after migrating to v78 of thunderbird, everything related to GPG worked just fine. Since a couple of weeks, I can not send any GPG encrypted emails any more. Still, I can receive GPG encrypted emails and they are being shown just fine. When I try to send an encrypted E-Mail, I get an error message:

"Senden der Nachricht fehlgeschlagen." (Failed to send message)

In the developer console, I see the following:

``` CryptoAPI.sync() failed result: Error: no suitable subkey found for encrypt

   addSuitableEncryptKey chrome://openpgp/content/modules/RNP.jsm:2200
   encryptAndOrSign chrome://openpgp/content/modules/RNP.jsm:2330
   sync chrome://openpgp/content/modules/cryptoAPI/interface.js:51
   encryptMessageStart chrome://openpgp/content/modules/encryption.jsm:341
   finishCryptoEncapsulation chrome://openpgp/content/modules/mimeEncrypt.jsm:571

interface.js:46:17 sendFlags=000050c2

mimeEncrypt.js: caught exception: Error Message: 'failure in finishCryptoEncapsulation' File: chrome://openpgp/content/modules/mimeEncrypt.jsm Line: 592 Stack: finishCryptoEncapsulation@chrome://openpgp/content/modules/mimeEncrypt.jsm:592:15 ``` My private key is ok (I use it since several years now with Thunderbird & Enigmail and GPG4Win) and I have selected the correct sub-key for each of my email accounts.

Can someone please help? I don't know what to do in order to make it work again...

Many thanks, Marc

Hello, after migrating to v78 of thunderbird, everything related to GPG worked just fine. Since a couple of weeks, I can not send any GPG encrypted emails any more. Still, I can receive GPG encrypted emails and they are being shown just fine. When I try to send an encrypted E-Mail, I get an error message: "Senden der Nachricht fehlgeschlagen." (Failed to send message) In the developer console, I see the following: ``` CryptoAPI.sync() failed result: Error: no suitable subkey found for encrypt addSuitableEncryptKey chrome://openpgp/content/modules/RNP.jsm:2200 encryptAndOrSign chrome://openpgp/content/modules/RNP.jsm:2330 sync chrome://openpgp/content/modules/cryptoAPI/interface.js:51 encryptMessageStart chrome://openpgp/content/modules/encryption.jsm:341 finishCryptoEncapsulation chrome://openpgp/content/modules/mimeEncrypt.jsm:571 interface.js:46:17 sendFlags=000050c2 mimeEncrypt.js: caught exception: Error Message: 'failure in finishCryptoEncapsulation' File: chrome://openpgp/content/modules/mimeEncrypt.jsm Line: 592 Stack: finishCryptoEncapsulation@chrome://openpgp/content/modules/mimeEncrypt.jsm:592:15 ``` My private key is ok (I use it since several years now with Thunderbird & Enigmail and GPG4Win) and I have selected the correct sub-key for each of my email accounts. Can someone please help? I don't know what to do in order to make it work again... Many thanks, Marc

所有回覆 (1)

more options

I think, I found something out: Thunderbird shows me, that the key has been expired at 2021-01-01. When I open the same key with Kleopatra, I can see that the key expires at 2030-03-01. As far as I remember, I enhanced the expiry date a year ago or so. So it seems like Thunderbird does not recognize the (new) expiry date but uses the old one - for whatever reason.

I exported the key once again from Kleopatra to a file and then imported it into Thunderbird and in the import process Thunderbird shows me that the key has expired at 2021-01-01.

I am not able to change the expiry date of this key in Thunderbird. I get an error message:

"Dies ist ein Schlüssel mit einer komplexen Struktur, das Ändern des Ablaufdatums wird nicht unterstützt." (this is a key with a complex structure, changing of the expiry date is not supported).

Even when I update the expire date to "never expires" via Kleopatra or the gpg command line tool and try to import it into Thunderbird the import dialog tells me that the key has expired at 2021-01-01.

Seems like this is a bug?

Any suggestions?

由 mpelzer 於 修改