Question about update

[sgpsistemas]

Good mornings,

We are contacting you from a company in Argentina. We currently use a Zimbra email server managed by a local provider.

In the last few days, following what we were informed was a Zimbra update on August 21, all users using Thunderbird as their email client began experiencing unusual behavior:

All IMAP mailboxes were downloaded from scratch, also affecting the Outlook client in addition to Thunderbird.

This caused a massive resynchronization, generating network slowness, temporary outages, and overloading user computers. Accounts configured as POP3 also did not work.

The issue occurred simultaneously in multiple accounts, only in external clients such as Thunderbird and Outlook.

We would like to confirm if:

There was an automatic and mandatory update on that date?

Has Zimbra documented any recent changes in patches or updates that may have caused a complete resynchronization of IMAP and POP3 accounts in clients such as Thunderbird and Outlook?

Are any fixes expected in future patches to prevent this from happening again?

We appreciate any official information you can provide, as we need to determine whether the problem is caused by the Zimbra update or by the administration of our local server.

We look forward to your response.

[liverpoolfcfan]

Zimbra should not force-update. It is likely an upgrade or patch was manually applied. However, the symptom you describe does not sound normal, even for updates.

Which Release/Patch level were you on previously?
Which Release/Patch level are you now running?

[sgpsistemas]

Good mornings

We migrate from Zimbra 9 to Zimbra 10.1

The server is managed by a local provider, so there's some information I don't have. What I'd like to know is whether a Zimbra update can be mandatory and automatic, and whether the resynchronization behavior I describe has been detected by other users and could indicate a bug in the final version.

[L. Mark Stone]

Good mornings

We migrate from Zimbra 9 to Zimbra 10.1

The server is managed by a local provider, so there's some information I don't have. What I'd like to know is whether a Zimbra update can be mandatory and automatic, and whether the resynchronization behavior I describe has been detected by other users and could indicate a bug in the final version.

Zimbra 9 went fully past end of life at the end of June (https://www.zimbra.com/product/product-lifecycle/).

A major version upgrade like that is always done manually.

Zimbra packages are repository based, so if the operating system is configured to update packages automatically ("unattended upgrades" in Ubuntu), then Zimbra and operating system patches will be applied automatically. I do not recommend this, as sometimes a patch's Release Notes contain new settings, decisions to be made, and/or other manual steps to be taken. I do recommend applying patches promptly--especially those containing security fixes.

Your server is likely (or should be) at 10.1.11. When Zimbra releases the next patch (10.1.12), and it is applied to your server, your IMAP clients will NOT be forced to resync all of their emails.

The major version upgrade resync you experienced is not a bug.

Hope that helps,
Mark

[ghen]

The major version upgrade resync you experienced is not a bug.

Is this behaviour documented somewhere?

[BradC]

if the operating system is configured to update packages automatically ("unattended upgrades" in Ubuntu), then Zimbra and operating system patches will be applied automatically.

The patches might be installed, but the unattended upgrades won't restart the relevant zimbra services automatically.

[adrian.gibanel.btactic]

All IMAP mailboxes were downloaded from scratch, also affecting the Outlook client in addition to Thunderbird.

We migrate from Zimbra 9 to Zimbra 10.1

This sounds like a FOSS installation moved from one cluster to another cluster with FOSS account dumps and some password ldap dumps (or maybe an external authentication system)... where the imap sync data would be lost.

I am curious to know if the accounts have kept their Zimbra preferences, including filters and signatures after the migration.

It can also be done in that FOSS-account-dump way even if you use NE but it's more unlikely.