Thunderbird 60.9.1 and 68.2.2 have been released

[harlan4096]

The Thunderbird development team has released two updates for the two supported branches of the email client. Thunderbird 60.9.1 and Thunderbird 68.2.2 are now available; both releases fix issues in the email client but don't introduce new features to it.

Thunderbird is offered in two versions currently. Thunderbird 60.x is the classic version of the email client while Thunderbird 68.x is the new version that is based on new code and as a result not fully compatible with all extensions released previously for the email client.

The team released Thunderbird 68 in August 2019 but did not include automatic update options from Thunderbird 60.x to the new version unless the calendar extension Lightning was installed. Thunderbird users may download the installer from the official project website to upgrade manually, but automatic upgrades are prevented unless the extension is installed.

Some users noticed that the profile that they were using in Thunderbird previously was not loaded after they made the upgrade to the new version. The profile contains all configured email services, all emails, installed extensions, and any other user data such as information about changed preferences.

Thunderbird 68.2.2

Thunderbird 68.2.2 fixes the upgrade issue that occurred when a 64-bit version of Thunderbird was upgraded from version 60 to 68.

Then upgrading a 64bit version of Thunderbird version 60 to version 68, the existing profile wasn't recognized and a new profile was created.
Note: If your profile is still not recognized, select it by visiting about:profiles in the Troubleshooting Information.
The new version has two unresolved issues according to the release notes:

Add-ons are updated automatically when Thunderbird 60 is upgraded to 68; this may disable some extensions even if compatible updates are available. Thunderbird users may open the Add-ons Manager to reinstall these if they are compatible with Thunderbird 68.
LDAP lookup is not working when SSL is enabled. Workaround: Disable SSL or switch off option "Query OSCP responder servers" in the certificate settings in advanced options.
...

Continue Reading