Zimbra 10.1.2 Released - Please Post Patch/Upgrade Results Here

[oetiker]

ZBUG-4317 (Autocomplete failure after updating to 10.1.1) is still not fixed in this release (classic and modern ui)
Product Management's comments on the bug: This bug has been classified as an S2 severity issue. We acknowledge its impact, and our engineering team is working on fixing the issue.

oetiker,

The current commits for the fix found here
https://github.com/Zimbra/zm-mailbox/pull/1660/commits

patch two files in the zm-mailbox repository
Provisioning.java
LdapProvisioning.java
...
...

Thanks for your effort, I will check that. I still can't believe that Zimbra does not release a fix for NE Customers for more than a month... and now waiting for another moth just that if fits in there release cycle.

[bulletxt]

Hello,

While testing 10.1.2 FOSS on unbuntu 20.04, it appears the 'send later' feature is broken.
After checking mailbox.log this might have started with 10.1.1.

If an email is scheduled to send later on the same day it will successfully deliver.
However if the scheduled date is the next day or later, the email will be deleted from the drafts folder without sending.

When a scheduled email is successfully delivered the log entries are

Code: Select all

[ScheduledTask-1] [] mailop - Adding Message:...
[ScheduledTask-1] [] smtp - Sending message to MTA at mail:...
[ScheduledTask-1] [] mailop - Deleting Message ...

When the scheduled delivery date is later than the current day the only entry is

Code: Select all

[ScheduledTask-2] [] mailop - Deleting Message ...

Hi, is this a known and confirmed bug?

[zmcontrol]

Hi, is this a known and confirmed bug?

bulletxt,

My only access is to search zimbra's github repositories.
At a glance I didn't notice any references to this bug.
I also searched the forums without success.

Are you able to confirm this bug in your environment?
I'm testing 10.1.2 FOSS on ubuntu 20.04.

[zmcontrol]

Thanks for your effort, I will check that.

oetiker,

Upon further testing this bug is now showing up on multiple accounts running 10.1.2 FOSS on ubuntu 20.04.
After replacing zimbrastore.jar with the patched version the bug remains.

When I have some time I will parse through the problematic accounts contacts to determine which fields are still causing this issue.

[L. Mark Stone]

Hi, is this a known and confirmed bug?

bulletxt,

My only access is to search zimbra's github repositories.
At a glance I didn't notice any references to this bug.
I also searched the forums without success.

Are you able to confirm this bug in your environment?
I'm testing 10.1.2 FOSS on ubuntu 20.04.

We too have had reports of Send Later not working as expected, resulting in data loss.

Specifically, a message queued up to be Sent Later is saved in the Drafts folder. The time for sending the message comes and goes. At the to-be-sent time the message is removed from the Drafts folder, but not sent. The message is not saved in Sent nor in Trash; the message is irretrievably lost.

We have advised our hosting customers that we are turning off the Send Later feature, and that they should either send those queued up messages now, or, save the contents somewhere else. It's not clear what happens when a message to be Sent Later is in the Drafts folder, and the feature is turned off before the message's time to be sent arrives.

Hope that helps,
Mark

[zmcontrol]

We too have had reports of Send Later not working as expected, resulting in data loss.

L. Mark Stone,

Thanks for your feedback and confirmation.

[zmcontrol]

When I have some time I will parse through the problematic accounts contacts to determine which fields are still causing this issue.

Hello,

After testing it appears the commits related to ZBUG-4317 (autocomplete failed) found here

https://github.com/Zimbra/zm-mailbox/pull/1660/commits

do resolve some of the problematic contacts fields but not all.
After applying the commits above the issue was resolved with some accounts, however it remained with others.

--
After applying the fixes, one way to determine which field(s) in a user's contacts that itriggers this bug is to:

Export the separate Contacts folders (Contact, Emailed Contacts, etc..) with type 'Account Contacts'.

Search the exported csv(s) for """ (three double quotes in a row).

Move all entries containing """ to the trash folder (contacts in the trash won't populate when autocompleting).

Verify if this resolves the issue.
--

Some observations..

'Contact Groups' will contain """ but shouldn't trigger this bug.

Since contacts in the trash folder are excluded from autocomplete, it's fast to test which entries are bad/good.

If a user creates a single contact, but includes more than one email address in the 'Email1' field it will trigger this bug.

Some entries in 'Emailed Contacts' had jacked up addresses in the 'Email' field that triggered this bug. For example:
,"""firstpart1@domain1.comfirstpart2""@domain2.com",
Somehow this field was parsed improperly at the time it was created.

[jzzr]

We too have had reports of Send Later not working as expected, resulting in data loss.

L. Mark Stone,

Thanks for your feedback and confirmation.

Hello,

Since version 8.8.15, we have a similar bug: if we restart the mailbox servers, the messages waiting in the drafts are lost.

Otherwise, even in version 10.1.2, if you don't restart the mailbox servers, the “send later” function works even the next day.

Do you restart mailbox servers every night?

[L. Mark Stone]

To my understanding, the Send Later defect has been assigned ZBUG-4384.

All users should be able to check its status in pm.zimbra.com shortly I would expect.

Network Edition users can check the status of any bug (but not a ZRFE) through the Support Portal.

Hope that helps,
Mark

[zmcontrol]

Do you restart mailbox servers every night?

jzzr,

Great catch! Yes in my environment mailboxd is stop/started once a day via zmcontrol.