Zimbra 10.1.13 Released - Please Post Your Patch/Upgrade Results Here

[adrian.gibanel.btactic]

Release Notes:
https://wiki.zimbra.com/wiki/Zimbra_Releases/10.1.13

Please post your patching and/or upgrading results here.

---

Zimbra NE 10.1.13 issues summary

( I don't usually do these summaries so... I'll give this warning: The descriptions here might not be accurate please check the links for the actual issues.

- RHEL7 upgrade of 10.1.13 is enabled (packages were pushed there) even if RHEL7 is EOL. That triggers 'grace period' regarding license and makes the system unusable. (Post)

- Amavisd does not start due to LD_LIBRARY_PATH not being set correctly or libraries not being linked properly at build time.
-- Amavisd not starting workaround.
-- Rocky Linux 9.6 is affected. (Post)
-- Rocky Linux 8.10 might not be affected. (Post)
-- Ubuntu 22.04 is affected. (Post1, Post2)

- Imap issues
-- Workaround fix for the Imap issues
-- MailStore (Imap client) having connection issues. (Post1)
-- Desktop email client has empty email body. (Post2, Post4)
-- Gmail app on Android has empty email body. (Post2, Post4)
-- Android clients no longer show up e-mail in readable form when connecting through IMAP. (Post3)
-- Applying filters with Thunderbird duplicates filtered messages several times. (Post3)
-- Outlook configured for IMAP. Problem accesing shared folders in non-local mailbox nodes. (Post5)
-- Mail on macOS takes a long time to display emails. (Post5)
-- Outlook IMAP issues. (Post6)

- Classic Web App attachment preview downloads the email instead of previewing it. (Post, Workaround). Update: According to updated release notes this is an intended behaviour (The PDF preview begin removed from Classic Web App) in order to avoid an XSS vulnerability associated with PDF attachments. So it's much better security-wise if you don't apply the workaround and just inform your final users.

- Some html emails are shown as blank pages. (Thread1, Thread2, Workaround (Unsafe))
- Ldap random crashes (with MMR enabled). (Post7)
- FOSS installations get broken when upgrading. (Post)

---

Please note that this is a Network Edition only release. It makes no sense to contribute ZCS FOSS 10.1.13 builds feedback in this thread because some of the 10.1.12 commits are embargoed. (Explanation.)

---

Update: Added Zimbra NE 10.1.13 issues ( 2025 11 09 22:15 UTC ).
Update: Added link to Imap Issues workaround ( 2025 11 11 09:30 UTC ).
Update: About preview issues in Classic UI being intended ( 2025 11 19 08:40 UTC ).
Update: Added link to amavisd not starting workaround ( 2025 11 20 10:10 UTC ).
Update: Added link to html emails are shown as blank pages threads. ( 2025 11 20 22:19 UTC ).
Update: Added link to Ldap random crashes (with MMR enabled) post. ( 2025 11 25 08:20 UTC ).
Update: Added link to html emails are shown as blank pages workaround. ( 2025 11 25 08:30 UTC ).

[oetiker]

Hi

I installed the patch. First impression is good. I have not noticed anything
bad till now.

Release 10.1.13.GA.4655.UBUNTU22_64 NETWORK edition.

And again no information about ZBUGs that have been fixed with the patch. My last support contact
filed a ZBUG about the ZBUG system on https://support.zimbra.com not showing current
status of ZBUGs.

We are sorry the inconvenience caused. I have reported the issue on (ZBUG-5183).
Reported Issue: ZBUG status not reflecting on "support portal".

(But this bug disappeared already)

It's truly an unfortunate strategy that Zimbra has adopted to keep users in the dark about bugs and their current status.
For example ZBUG-5100 is still marked as open and was fixed with this release.

Bug Number: ZBUG-5100
Status: Open
Summary:
Clam-av has critical vulnerabilities

[jackpeter]

Update was NOT successfull. After install following services ar not running anymore -> zmmailboxdctl.
And Licence was again changed into 'grace period' even when it's subscribed and active.. normale procedure started: contacted support and wait for instructions.

Recomend to be carefull with update on productive-systems...

[uttam.takalkar]

Hi

I installed the patch. First impression is good. I have not noticed anything
bad till now.

Release 10.1.13.GA.4655.UBUNTU22_64 NETWORK edition.

And again no information about ZBUGs that have been fixed with the patch. My last support contact
filed a ZBUG about the ZBUG system on https://support.zimbra.com not showing current
status of ZBUGs.

We are sorry the inconvenience caused. I have reported the issue on (ZBUG-5183).
Reported Issue: ZBUG status not reflecting on "support portal".

(But this bug disappeared already)

It's truly an unfortunate strategy that Zimbra has adopted to keep users in the dark about bugs and their current status.
For example ZBUG-5100 is still marked as open and was fixed with this release.

Bug Number: ZBUG-5100
Status: Open
Summary:
Clam-av has critical vulnerabilities

ZBUG-5100 is closed and clam-av upgraded to 1.4.3

[oetiker]

Here the screenshot from today

2025-11-06_12-08.png (33.57 KiB) Viewed 2617 times

[uttam.takalkar]

Here the screenshot from today

2025-11-06_12-08.png

we are working in status sync with Bug lookup. but clam-av has been upgraded and we have closed that bug in this patch.

[adrian.gibanel.btactic]

Update was NOT successfull.

Which OS version (Ubuntu 22.04, RHEL9, etc.) are we talking about?

I'm wondering if this is the usual binary package repo sync issues that sometimes happen at the very start of a new release. Maybe it only affects CentOS and not Ubuntu (or viceversa).

[jackpeter]

RedHat Enterprise 7.6
i keep on waiting for reaction for my ticket in support-case-portal.

[sylon]

Heyho

After patching from 10.1.11 to 10.1.13 and then updating the system, we encountered the problem that amavisd would no longer start because LD_LIBRARY_PATH was missing.

Result:

Code: Select all

Starting amavisd...Can't load '/opt/zimbra/common/lib/perl5/x86_64-linux-thread-multi/auto/Net/SSLeay/SSLeay.so' for module Net::SSLeay: /lib64/libcrso.3) 
at /usr/lib64/perl5/DynaLoader.pm line 193. at /opt/zimbra/common/lib/perl5/IO/Socket/SSL.pm line 19. 
Compilation failed in require at /opt/zimbra/common/lib/perl5/IO/Socket/SSL.pm line 19. 
BEGIN failed--compilation aborted at /opt/zimbra/common/lib/perl5/IO/Socket/SSL.pm line 19. 
Compilation failed in require at /opt/zimbra/common/lib/perl5/Amavis/IO/RW.pm line 18. 
BEGIN failed--compilation aborted at /opt/zimbra/common/lib/perl5/Amavis/IO/RW.pm line 18. 
Compilation failed in require at /opt/zimbra/common/lib/perl5/Amavis/DKIM.pm line 34. 
BEGIN failed--compilation aborted at /opt/zimbra/common/lib/perl5/Amavis/DKIM.pm line 34. 
Compilation failed in require at /opt/zimbra/common/lib/perl5/Amavis.pm line 7190. failed.

later i get

Code: Select all

Starting amavisd...Can't load '/opt/zimbra/common/lib/perl5/x86_64-linux-thread-multi/auto/Net/SSLeay/SSLeay.so' for module Net::SSLeay: /lib64/libcrypto.so.3: version `OPENSSL_3.3.0' not found (required by /opt/zimbra/common/lib/libssl.so.3) at /usr/lib64/perl5/DynaLoader.pm line 193.
 at /opt/zimbra/common/lib/perl5/IO/Socket/SSL.pm line 19.
Compilation failed in require at /opt/zimbra/common/lib/perl5/IO/Socket/SSL.pm line 19.
BEGIN failed--compilation aborted at /opt/zimbra/common/lib/perl5/IO/Socket/SSL.pm line 19.
Compilation failed in require at /opt/zimbra/common/lib/perl5/Amavis/IO/RW.pm line 18.
BEGIN failed--compilation aborted at /opt/zimbra/common/lib/perl5/Amavis/IO/RW.pm line 18.
Compilation failed in require at /opt/zimbra/common/lib/perl5/Amavis/DKIM.pm line 34.
BEGIN failed--compilation aborted at /opt/zimbra/common/lib/perl5/Amavis/DKIM.pm line 34.
Compilation failed in require at /opt/zimbra/common/lib/perl5/Amavis.pm line 7190.
failed.

Apparently, the use of LD_LIBRARY_PATH was unset in .bashrc of the user zimbra

After inserting

Code: Select all

export LD_LIBRARY_PATH=/opt/zimbra/common/lib

and commenting

Code: Select all

#unset LD_LIBRARY_PATH

out, amavisd started again without any problems, as did the complete restart of Zimbra.

What remained was the very long user change from root to Zimbra since the paching.

Still waiting for answer from Customer Support Portal (case 01896967).

in case of interest (cat /etc/*release ):

Code: Select all

NAME="Rocky Linux"
VERSION="9.6 (Blue Onyx)"
ID="rocky"
ID_LIKE="rhel centos fedora"
VERSION_ID="9.6"
PLATFORM_ID="platform:el9"
PRETTY_NAME="Rocky Linux 9.6 (Blue Onyx)"
ANSI_COLOR="0;32"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:rocky:rocky:9::baseos"
HOME_URL="https://rockylinux.org/"
VENDOR_NAME="RESF"
VENDOR_URL="https://resf.org/"
BUG_REPORT_URL="https://bugs.rockylinux.org/"
SUPPORT_END="2032-05-31"
ROCKY_SUPPORT_PRODUCT="Rocky-Linux-9"
ROCKY_SUPPORT_PRODUCT_VERSION="9.6"
REDHAT_SUPPORT_PRODUCT="Rocky Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="9.6"
Rocky Linux release 9.6 (Blue Onyx)

Does anyone know why LD_LIBRARY_PATH is unset in .bashrc?

cheers

[adrian.gibanel.btactic]

RedHat Enterprise 7.6
i keep on waiting for reaction for my ticket in support-case-portal.

As Bradc pointed out recently that OS reached end-of-life in ZCS 10.1.10.