Closed Bug 1780448 Opened 2 years ago Closed 2 years ago

Signing mails with S/MIME doesn't work anymore.

Categories

(MailNews Core :: Security: S/MIME, defect)

Thunderbird 102
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1777336

People

(Reporter: msaluz, Unassigned)

Details

Attachments

(1 file)

Attached image Error1.png

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.5060.114 Safari/537.36 Edg/103.0.1264.62

Steps to reproduce:

I did a mail with S/MIME signing.

  • generate mail
  • S/MIME signing

Actual results:

I got an error message that E-Mail cannot be sent.
I also missed the certificate sign which was in former version.

Expected results:

Mail should be signed with the same certificate which is successfully used with former versions of Thunderbird.

Component: Message Compose Window → Security: S/MIME
Flags: needinfo?(kaie)
Product: Thunderbird → MailNews Core

Mario, maybe you are affected by bug 1777336.

Please try again using Thunderbird 102.0.3, or, if you cannot yet upgrade to that version, you may try the workaround described in the whiteboard section in bug 1777336

Flags: needinfo?(kaie) → needinfo?(msaluz)

Hi Kai
I could fix the problem with the workaround of bug 1777336.
102.0.3 was already installed.
security.intermediate_preloading_healer.enabled was already set to false.
Initially I still had the error. But after I opened a former sent signed mail it works.
It worked also after I closed Thunderbird and rebooted the system
I could reproduce it on two windows 10 systems.
For me the problem is solved with the workaround.
Thanks. I appreciate your help.

Flags: needinfo?(msaluz)

thanks for the feedback

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: