Autocomplete behaviour change between 9.0 and 10.1

[liverpoolfcfan]

I don't think it's strategic as such. More likely Hanlon's razor applies.

That's a new one on me. I like it!

[oetiker]

Hi

Answer from: July 4, 2025 9:23 PM

Your case has resulted in a BUG, and you can check the status in the support portal using ZBUG-4975. When you log into your support account (in [https://support.zimbra.com] ), select Support > Bug Lookup. Here you can:
- See status and release version (if one has been assigned).
- Provide feedback, escalate, and ask for a status. If there isn't a status, the Zimbra Team will follow up with you.

I did escalate but nothing happens at all ... 3 Month later still no fix no plan no information ...

I like a lot about zimbra but this part not at all ...

[gabrieles]

Does anyone have the patched .jar? Can we place it on publicly accessible storage without time restrictions, at least until the zbug is fixed?

[andrey.ivanov]

Yes, i continue to maintain for our systems the patched jar according to the principles described in this thread (replacement of a single .class in the production/stock Network Edition jar).

You can compare my .jar with the stock .jar by "unzipping" the archive (with "jar xf filename.jar"). The only difference should be the file ContactAutoComplete.class contained in this archive.

I have uploaded the up-to-date file zimbrastore-patched-10.1.14.jar (to replace /opt/zimbra/lib/jars/zimbrastore.jar) here: https://filesender.renater.fr/?s=downlo ... 22350c3921

sha256sum of this file is b4a0ebe22479abe95d89a9cbd5c4ead0611d7f609cdb46402df2788290c5840e

[gabrieles]

Thanks adnrey for the jar and sorry for the late response but we were testing extensively.

We tested it, and our own jar with the same modification, in a multiserver installation with many domains, one of them having an External GAL configured.
We found your behaviour even in this case > while ALL accounts from external LDAP GAL are shown and appear in autocompletion.

It doesn't seems related to the jar, but to the presence of the jar on any mailstore of the isntallation, sepcifically on the mailstore where resides the account using the webmail, AND the mailstore where resides the galsync@ account.
Deploying the jar on each mailstore seems to solve the unwanted autocompletion.

[7224jobe]

Hello, posting just to confirm that this annoying bug is still here on latest version 10.1.15

[7224jobe]

Hi, since Zimbra is not fixing this issue at the moment, can anyone re-share the patched .jar made by andrey.ivanov? All download links in this thread are expired.
Thanks!

[andrey.ivanov]

Hi, since Zimbra is not fixing this issue at the moment, can anyone re-share the patched .jar made by andrey.ivanov? All download links in this thread are expired.
Thanks!

Hi,

sure, i can re-upload it (it's ths same file for 10.1.13, 10.1.14 and 10.1.15). Here you go : https://filesender.renater.fr/?s=downlo ... fc49366cd9
sha256sum of this file is b4a0ebe22479abe95d89a9cbd5c4ead0611d7f609cdb46402df2788290c5840e

You can compare my .jar with the stock /opt/zimbra/lib/jars/zimbrastore.jar by "unzipping" the archive (with "jar xf filename.jar"). The only difference should be the file ContactAutoComplete.class contained in this archive.

Regards,
AI

[ghen]

I have spent a couple of days troubleshooting this problem. Its origin is in the file zm-mailbox/store/src/java/com/zimbra/cs/mailbox/ContactAutoComplete.java. I have patched this file and recompiled from sources (using for example Dunphy's build helpers, thanks a lot Dunphy!!!! - https://wiki.zimbra.com/wiki/JDunphy-Co ... mbraScript).

Then i have replaced the compiled patched file ./com/zimbra/cs/mailbox/ContactAutoComplete.class in the production /opt/zimbra/lib/jars/zimbrastore.jar and it fixed our problem.

Hi Andrey
The wiki link doesn't work anymore. Are you building all of Zimbra from scratch, or just the modified classfiles?
I'm also rebuilding zimbrastore.jar (for a different problem, reverting this change), but I'm building just Mailbox.java and MailItem.java with direct javac invocation.

[andrey.ivanov]

I have spent a couple of days troubleshooting this problem. Its origin is in the file zm-mailbox/store/src/java/com/zimbra/cs/mailbox/ContactAutoComplete.java. I have patched this file and recompiled from sources (using for example Dunphy's build helpers, thanks a lot Dunphy!!!! - https://wiki.zimbra.com/wiki/JDunphy-Co ... mbraScript).

Then i have replaced the compiled patched file ./com/zimbra/cs/mailbox/ContactAutoComplete.class in the production /opt/zimbra/lib/jars/zimbrastore.jar and it fixed our problem.

Hi Andrey
The wiki link doesn't work anymore. Are you building all of Zimbra from scratch, or just the modified classfiles?
I'm also rebuilding zimbrastore.jar (for a different problem, reverting this change), but I'm building just Mailbox.java and MailItem.java with direct javac invocation.

Hi Ghen,

The original wiki is here : https://web.archive.org/web/20250517034 ... mbraScript

**** Synacor employee Yogesh Dasi recently deleted the above wiki article. Why? no reason was given. ****
I would like to know the reason why Synacor employee has deleted it, it was extremely useful and detailed.

The original script from that wiki that I was using is here: https://github.com/JimDunphy/build_zimbra.sh . But you can use whatever build process you like. Yes, I rebuild from scratch the closest Zimbra tag from the official git, changing only one source file, and then compare the contents of the resulting compiled .jar with the same production .jar. The difference should be only the .class file that was modified (ContactAutoComplete.class in my case). If that is the case, as a precaution, I repack the original .jar, identical but with the new class. Here is an example bash code for extraction of the compiled .rpm and obtaining the final .jar:

Code: Select all

# Build Zimbra
bash build_zimbra_with_patch_Dunphy.sh --clean --version 10.1.8

mkdir /tmp/extract
cp BUILDS/RHEL8_64-DAFFODIL_T100108C100106FOSS-1018-20250611133029-FOSS-1011001/zcs-10.1.8_GA_1011001.RHEL8_64.20250611133029.tgz /tmp/extract/
cd /tmp/extract/
tar xzf zcs-10.1.8_GA_1011001.RHEL8_64.20250611133029.tgz
cp zcs-10.1.8_GA_1011001.RHEL8_64.20250611133029/packages/zimbra-common-core-jar-10.1.8.1745958496-1.r8.x86_64.rpm .
rm -fr zcs-10.1.8_GA_1011001.RHEL8_64.20250611133029*
mkdir unbundle-rpm
cd unbundle-rpm/
mv ../zimbra-common-core-jar-10.1.8.1745958496-1.r8.x86_64.rpm  .
rpm2cpio zimbra-common-core-jar-10.1.8.1745958496-1.r8.x86_64.rpm | cpio -idmv
mv opt/zimbra/lib/jars/zimbrastore.jar /tmp/extract/zimbrastore-patched.jar
cd /tmp/extract/
rm -fr unbundle-rpm/
mkdir MY
cd MY
jar xf ../zimbrastore-patched.jar 
mkdir ../COMMERCIAL
cd ../COMMERCIAL/
# Take /opt/zimbra/lib/jars/zimbrastore.jar from PRODUCTION server
jar xf ../zimbrastore-original-10.1.8.jar
cat ../MY/com/zimbra/cs/mailbox/ContactAutoComplete.class  > ./com/zimbra/cs/mailbox/ContactAutoComplete.class
jar cMf zimbrastore-patched.jar *


# This is the patched zimbrastore.jar
# cp zimbrastore-patched.jar /tmp