S/MIME Failures - 102
I've noticed in version 102 that when I send an S/MIME signed email that I get "Digital Signature is Not Valid" errors. This happens on the copy I received that is BCCed, but not on the copy saved in the sent folder. I have verified with the recipient that they get an error when they read the message.
I launched Thunderbird 102.6.1 into Safe mode, and the problem persisted.
The certificate is good through 2025.
All Replies (7)
This happens on multiple machines - two MacBook Pros and one Apple Studio, all using Ventura 13.1. Note that this issue has persisted over the last few MacOSs.
Check the received message and compare the contents with the message you sent. It's possible your email provider added e.g. some sort of advertising to the message, which would cause the "Digital Signature is Not Valid" error.
The received message is the same as the sent message except in the MIME headers:
Saved sent message:
Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
and the BCC received message is:
Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64
Could changing from 8bit coding to base64 coding be the problem? I just checked Bugzilla and found this: https://bugzilla.mozilla.org/show_bug.cgi?id=1794768
Could changing from 8bit coding to base64 coding be the problem?
Yes, I think so. But I'm not sure why the coding changes.
You've updated the Bugzilla entry 1794768. How can I see if the fix is on the roadmap, the status, or anything else helpful?
Just watch the bug. If there is any activity you'll see it there.
As a workaround you can try to set the pref mail.strictly_mime to true. This will enforce 'quoted-printable' content transfer encoding.