This Gist describes how to update the max version number of TBSync and EAS Provider above ESR version.
Attention: This process does not ensure the Extension works after update, if breaking changes appear.
Before you are able to execute the script below you need to download the latest version of TBsync and any provider you like to patch from the list below:
Afterwards update the script matching the version numbers.
| #!/usr/bin/env bash | |
| set -euo pipefail | |
| # UPGRADE IF NECESSARY | |
| LATEST_TBSYNC_VERSION=4.16 | |
| LATEST_EAS_VERSION=4.17 | |
| TARGET_TB_VERSION=142 | |
| if [ -f tbsync-$LATEST_TBSYNC_VERSION-tb.xpi ]; then | |
| unzip -qq tbsync-$LATEST_TBSYNC_VERSION-tb.xpi -d tbsync_src | |
| jq ".applications.gecko.strict_max_version=\"$TARGET_TB_VERSION.*\"" tbsync_src/manifest.json > manifest.json 2>&1 | |
| if [ $? -ne 0 ]; then | |
| echo "Error while updating TBsync manifest. Please update tbsync_src/manifest.json manually" | |
| fi | |
| zip -u tbsync-$LATEST_TBSYNC_VERSION-tb.xpi manifest.json | |
| else | |
| echo "No TBSync Extension Provided. Skipping!" | |
| fi | |
| if [ -f provider_fur_exchange_activesync-$LATEST_EAS_VERSION-tb.xpi ]; then | |
| unzip -qq provider_fur_exchange_activesync-$LATEST_EAS_VERSION-tb.xpi -d eas_src | |
| jq ".applications.gecko.strict_max_version=\"$TARGET_TB_VERSION.*\"" eas_src/manifest.json > manifest.json 2>&1 | |
| if [ $? -ne 0 ]; then | |
| echo "Error while updating EAS manifest. Please update eas_src/manifest.json manually" | |
| fi | |
| zip -u provider_fur_exchange_activesync-$LATEST_EAS_VERSION-tb.xpi manifest.json | |
| else | |
| echo "No EAS Extension Provided. Skipping!" | |
| fi | |
| echo "You are now able to install the xpi to Thunderbird <= $TARGET_TB_VERSION!" | |
| echo | |
| echo "If an Error appears, like corrupted xpi file, you might need to start over." | |
| # Cleanup | |
| rm -rf tbsync_src | |
| rm -rf eas_src | |
| rm -rf manifest.json |
https://www.thunderbird.net/en-US/thunderbird/145.0/releasenotes/
Enable support for Microsoft Exchange via Exchange Web Services
145 added native Exchange support, so that may be why. I think there are some limitations though: https://blog.thunderbird.net/2025/11/thunderbird-adds-native-microsoft-exchange-email-support/
Yes I already thought the same. This was original the case why I have updated. No Calendar for me at the moment.
Just to let anybody know: I am unable to use the Release for 140.X ESR on TB145.X Seems they changed a lot more...