Thunderbird 102.0.3 update fixes a crash on Windows 11

Martin Brinkmann
Jul 22, 2022
Thunderbird
|
7

The Thunderbird team has released Thunderbird 102.0.3 Stable. The new version of the open source email client fixes a crash on Windows 11 and several other issues in previous versions of the application.

thunderbird 102
image credit: Thunderbird

Thunderbird 102.0.3 is already available, either as an in-client upgrade or a manual download from the official project website. Only Thunderbird 102.x installations can be upgraded to the new version. Older Thunderbird installations do not get the upgrade offer to version 102 at this point, but this is going to change in the future.

Thunderbird 102.0.3

thunderbird 102.0.3

Select Help > About Thunderbird to display the current version and check for updates. If the menubar is not displayed, tap on the Alt-key on the keyboard to display it. The client should pick up the update automatically. A restart is required to complete the installation of the update.

ADVERTISEMENT

The official changelog lists 12 changes that made it into Thunderbird 102.0.3. Windows users who run Thunderbird 102 on Microsoft's Windows 11 operating system may have hade the client crash on startup; this issue has been fixed in the new release.

The only change listed in the changelog is the removal of support for Google Talk chat accounts. Thunderbird 102 supports Matrix, Odnoklassniki, IRC and XMPP currently.

Access to downloaded messages was not provided in previous versions of Thunderbird after folders were compacted by the client. Compacting reduces the storage that Thunderbird requires on the local device. The developers have addressed the issue in the new release.

The following fixes are also listed:

  • When using Unified Folders, marking a message as a favorite (starring it) did not update the thread pane.
  • When S/MIME was configured, Compose failed to populate some fields.
  • The incorrect mime header charset=windows-1250 was set for non-text attachments.
  • The incorrect header X-Mozilla-Cloud-Part was set for messages sent as attachments.
  • Address book importing and exporting has been improved in the profile importer.
  • Unspecified IMAP stability improvements.
  • Addressed an issue that made the offline cache unusable for NNTP accounts.
  • Signing S/MIME messages failed.
  • Unspecified UI improvements.

Thunderbird 102.0.3 is the third point release of version 102 of the email client. Thunderbird 102 was a major new release with a large list of improvements and new features. The point releases 102.0.1 and 102.0.2 addressed issues in the new version, similarly to version 102.0.3.

Now You: do you use Thunderbird 102 already?

 

Summary
Thunderbird 102.0.3 update fixes a crash on Windows 11
Article Name
Thunderbird 102.0.3 update fixes a crash on Windows 11
Description
The Thunderbird team has released Thunderbird 102.0.3 Stable. The new version of the open source email client fixes a crash on Windows 11 and several other issues in previous versions of the application.
Author
Publisher
Ghacks Technology News
Logo
Advertisement

Previous Post: «
Next Post: «

Comments

  1. Occasional TB user said on July 22, 2022 at 11:24 am
    Reply

    Thunderbird 102.x does not allow me to connect to my local Dovecot IMAP server and I see this error in the server’s mail log file:

    imap-login: Disconnected: Connection closed: SSL_accept() failed:
    error:0A000412:SSL routines::sslv3 alert bad certificate: SSL alert
    number 42 (disconnected before auth was ready, waited 0 secs): user=,
    rip=XXX.XXX.XXX.XXX, lip=XXX.XXX.XXX.XXX, TLS handshaking: SSL_accept()
    failed: error:0A000412:SSL routines::sslv3 alert bad certificate: SSL
    alert number 42

    Downgrade to Thunderbird 91.x or 68.x solves the problem. Notably, other mail clients (Gnus, Claws-Mail, mutt) have no problem to connect. I guess, it’s a bug that was introduced in TB 102. A brief search revealed that this problem occurred for other versions of TB in the past as well. Playing around with OCSP settings (as sometimes suggested) did not help.

    1. Frankel said on July 22, 2022 at 1:36 pm
      Reply

      The problem is entirely self made. Why do you run a local server? Anyways it literally tells you that you use a bad cert. Whitelist your self-signed cert in the NSS libs/API. Or stop running local servers. How about a real server with a real DNS entry and access that via domain.

      Just some food for thought. There is hacks and there is the professional’s way. But i am happy your security downgrade works so good!

      1. Occasional TB user said on July 22, 2022 at 1:48 pm
        Reply

        Unfortunately, all your assumptions are wrong.

        It is a real server with a real DNS entry with a real domain. And of course self signed certificates must never cause a problem. One just needs to accept the certificate by adding it to the exception list. However, TB 102 does not reach this point asking for the certificate.

        Besides, it’s also the wrong approach: The certificate hasn’t changed at all and older TB versions successfully connect to the Dovecot IMAP server, just as *every* other legit MUA. TB has been updated from 91.x to 102.x , not the Dovecot server and not the certificate (which is still valid for several years).

        Clearly a TB bug …

      2. VB5 said on July 22, 2022 at 5:55 pm
        Reply

        Report it to the developers then…

      3. Occasional TB user said on July 25, 2022 at 1:52 pm
        Reply

        As my name says, TB is not my main MUA and I just use it occasionally. Since I don’t have a bugzilla account and I’m not going to create one for this issue, I’m not going to report it there.

        I only mentioned it here for the sake of completeness. My regular MUAs perfectly interact with the Dovecot IMAP sever.

        JFTR, it’s an older bug that was already reported, closed as fixed and re-introduced now: https://bugzilla.mozilla.org/show_bug.cgi?id=1629416

      4. Frankel said on July 23, 2022 at 10:49 am
        Reply

        Useless to argue about this without knowing what versions of the protocol you run, if the clocks on the systems are set correctly and you don’t use outdated TLSv1.1 or any other standard that is not TLSv1.3

        Just because it works on an old version doesn’t mean it is “a bug”. Sounds more like me it doesn’t want to connect to deprecated protocols. Why? Because I can access 5 different email provides perfectly fine on my TB.

  2. abhem said on July 24, 2022 at 1:56 pm
    Reply

    when Thunderbird series version 102 there is security fixes, then jumped from Thunderbird version 91.11.0

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

We love comments and welcome thoughtful and civilized discussion. Rudeness and personal attacks will not be tolerated. Please stay on-topic.
Please note that your comment may not appear immediately after you post it.