2.79.5 (2026-08-26)
Repairs the auth-failure safety net for OAuth2 accounts, which 2.79.3 extended and 2.79.4 only partly fixed. Upgrading is recommended for anyone who has run either release.
Accounts switched off by 2.79.3 can be recovered again. In the window between 2.79.3 and 2.79.4, every OAuth2 account whose refresh token had already been dead for longer than the three-day threshold was switched off in one burst, and the reason was recorded in a way that 2.79.4 reads as a deliberate send-only account. Re-authorizing such an account reported success without resuming it, and a Gmail API or Outlook account had no control on its page that reached the flag at all. A one-time migration now runs at startup and marks that population, so re-authorization and "Resume syncing" work on it again. No manual action is required.
Switching an account off could take down an IMAP worker. For a Gmail API or Outlook account, the connection shutdown that follows the switch-off could fail in a way that stopped the worker and every account it was handling, until the next restart.
Also fixed:
- An account registered with
imap: falsewas never switched off at all, so a dead refresh token kept being retried indefinitely. - A delegated account, such as an Outlook shared mailbox, was switched off over authentication failures of the account it borrows its credentials from, and re-authorizing that account did not bring it back.
- Saving new IMAP credentials did not resume a switched-off account, although the API documents that it does.
- A switched-off account was reported as send-only, which hid both its connection settings and the error explaining why it stopped syncing.
- Re-registering an existing password account with OAuth2 left the previous IMAP configuration in place, and its disable flag then silently kept the account from syncing.
- The accounts list showed a neutral "Not syncing" for accounts that releases before 2.79.4 had switched off.