Sunday, November 22, 2026
TR
Linux

Zimbra Joule 8.8.15 Patch 33 GA Release

Zimbra Joule 8.8.15 Patch 33 GA Release
Contents
  1. Change in the Upgrade Process for 8.8.15 Patch 33
  2. Changes Required for SSO Setup Before the Patch Upgrade
  3. Security Fixes
  4. Package Upgrades
  5. Zimbra Web Client (ZWC)
  6. Zimbra Connector for Outlook
  7. Zimbra Collaboration
  8. Zimbra Web Client (ZWC)
  9. Zimbra Connector for Outlook
  10. NG Authorization
  11. NG Backup
  12. NG HSM
  13. 8.8.15 Patch 33 Packages
  14. ubuntu
  15. Jira Tickets Fixed in Joule 8.8.15 Patch 33

For this release of Zimbra Collaboration, see the Security Fixes , What's New , Fixed Issues and Known Issues sections . For patch installation instructions, please see the Patch Installation section . As always, you are encouraged to tell us what you think in the Forums or to open a support ticket to report issues.

NOTE: If you are upgrading an older version of Zimbra to Zimbra 8.8 Production Ready, or moving to Zimbra 8.8 Production Ready from this release, please read Things to Know Before Upgrading and First Steps with the Zimbra NG Modules for critical information before upgrading.

Change in the Upgrade Process for 8.8.15 Patch 33

Please note that the installation process has changed. Additional steps to install the zimbra-common-core-jar, zimbra-common-core-libs and zimbra-mbox-store-libs packages have been added to this patch release. To install the packages in order, see the Patch Installation section .

Changes Required for SSO Setup Before the Patch Upgrade

Before upgrading, we need to set the zimbraVirtualHostName parameter for domains that use SAML and SSO-based login . Please follow the instructions:

su - zimbra
zmprov md domain_name zimbraVirtualHostName virtual_hostname

Security Fixes

SummaryCVE IDCVSS ScoreZimbra Rating
Upgraded OpenSSL to 1.1.1q to avoid multiple vulnerabilitiesCVE-2022-20689.8Low
RXSS on '/h/search' via the Title parameterCVE-2022-37044TBDLow
RXSS on '/h/search' via the onload parameterCVE-2022-37044TBDMedium
RXSS on '/h/search' via the Extra parameterCVE-2022-37044TBDMedium
Authentication Bypass in MailboxImportServletCVE-2022-37042TBDHigh
Proxy Servlet SSRF VulnerabilityCVE-2022-37041TBDLow
Cyrus SASL package upgraded to version 2.1.28CVE-2022-244078.8Low
When using preauth, CSRF tokens are not checked on some post endpoints.CVE-2022-37043TBDMedium

What's New

Zimbra 8.8.15 is now fully supported on Rocky Linux 8 (GA)

Download the latest Rocky Linux 8 binaries from https://www.zimbra.com/downloads 

Package Upgrades

  • OpenSSL was upgraded to version 1.1.1q
  • Cyrus SASL package was upgraded to version 2.1.28

Zimbra Web Client (ZWC)

  • In the previous patch release, a local configuration attribute allow_username_within_password was introduced to restrict users from using their usernames in the password in the Modern Web App. With this patch release, the feature is available for the Classic Web App. It will restrict users from using their names when resetting or changing the password.

Zimbra Connector for Outlook

  • ZCO is now supported on the Windows 11 platform.
  • The old auto-complete cache is now detected automatically when synchronization occurs, and when YES is selected, the user is now prompted with a Yes/No dialog to automatically clear the old cache.
  • Users were unable to schedule a meeting through MS Teams when they clicked the "New Teams Meeting" option. The issue has been fixed.

Fixed Issues

Zimbra Collaboration

  • The XML declaration was updated in the EWS response for clients to consume.
  • Spamassassin's zmsaupdate script was updated to remove the –allowplugins option .
  • In the previous patch, a feature was introduced to add an external message warning header when receiving email from external domains. In certain scenarios, it caused high CPU usage. The issue has been fixed.
  • On the Ubuntu 20 operating system, restarting the zmmailboxdctl service printed a harmless error on the console. The issue has been fixed.
  • Due to the log4j changes in the previous patch, in a multi-node environment the /var/log/messages file was being continuously updated with INFO logs. The issue has been fixed and the default log level is now set to ERROR.
  • Due to the log4j changes in the previous patch, Syslog shipping was enabled by default, continuously updating the /var/log/syslog file . The issue has been fixed and Syslog shipping has been disabled.
  • In a multi-node environment, if a user had enabled and set up 2FA and selected "Trust this computer" on the login screen, the setting did not persist and the user was asked to enter the OTP. The issue has been fixed.

Zimbra Web Client (ZWC)

  • Intermittently, when a user shared a specific folder from the Classic Web App, the root folder was shared. The issue has been fixed.
  • If a user has multiple calendars and, while viewing the Calendar tab in day view, double-clicks on a non-default calendar to create an event, the default calendar is selected. The issue has been fixed.

Zimbra Connector for Outlook

  • An error was encountered when a user tried to send an email through a shared mail folder that had the SendAs right. The issue has been fixed.

NG Authorization

  • A password change will no longer be taken into account when using application credentials or QR code-based authentication for applications.

NG Backup

  • A bug that prevented the S3 backup volume from being updated was fixed.
  • Error handling was improved when running a purge and the ZxBackup_DataRetentionDays attribute has an invalid value.
  • A new backupSkipDLAndDynamicGroups attribute was added, so it is now possible to skip the backup of distribution lists and dynamic groups to improve backup time.
  • A bug that caused accounts' metadata to be mistakenly uploaded to the root folder of the bucket was fixed. Metadata files are now properly uploaded to the accounts folder.

NG HSM

  • A bug that prevented the S3 backup volume from being updated was fixed. A bug that prevented blobs from being purged from the central volume when a mailbox was moved from a server that has said central volume configured to another server that does not have it was fixed.

Known Issues

  • If you encounter the following error while installing Zimlets, see the Patch Installation section, install the zimbra-common-core-jar, zimbra-common-core-libs, zimbra-mbox-store-libs packages in the specified order, and redeploy the Zimlets.
/opt/zimbra/bin/zmjava: line 59: /bin/java: No such file or directory
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/logging/log4j/core/appender/ConsoleAppender$Target
       at com.zimbra.cs.localconfig.LocalConfigCLI.main(LocalConfigCLI.java:353)
Caused by: java.lang.ClassNotFoundException: org.apache.logging.log4j.core.appender.ConsoleAppender$Target
       at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:602)
       at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
       at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
       ... 1 more
  • Starting with Joule-Patch-32, customers using TOA will need to update the zimbraVirtualHostName attribute for their domains . To update the attribute, please see the instructions .
  • With JDK 17, weaker Kerberos encryption types such as 3DES and RC4 are now disabled by default. This may cause SPNEGO authentication to fail if the described encryption types are used. We recommend using stronger encryption types such as AES256.

To make SPNEGO authentication work with weak encryption types, weak crypto can be enabled by setting the allow_weak_crypto property to true in the krb5.conf configuration file . Please follow the instructions below:

1. Set allow_weak_crypto = true in the /opt/zimbra/jetty_base/etc/krb5.ini.in -> [libdefaults] section

2. Restart the mailboxd service:

su - zimbra
zmmailboxdctl restart

Patch Installation

To install on Ubuntu platforms, please refer to the steps below:

Consider the Following Before Installing the Patch:

  • Patches are cumulative.
  • A full backup should be performed before any patch is applied. There is no automatic rollback.
  • Zimlet patches may involve removing the existing Zimlets and redeploying the patched Zimlet.
  • Only files or Zimlets associated with installed packages will be installed from the patch.
  • Switch to the zimbra user before using ZCS CLI commands.
  • Important! You cannot revert to the previous ZCS version after upgrading to the patch.
  • Important! Please note that the installation process has changed. Additional steps to install the zimbra-common-core-jar, zimbra-common-core-libs and zimbra-mbox-store-libs packages have been added to this patch release. To install the packages in order, see the Patch Installation section .

8.8.15 Patch 33 Packages

Package list for this release:

FOSS:

PackageName			           	Version
zimbra-patch				->	8.8.15.1658841204.p33-2
zimbra-mta-patch			->	8.8.15.1658841204.p33-1
zimbra-mta-components			->	1.0.15-1zimbra8.8b1
zimbra-proxy-patch			-> 	8.8.15.1658841204.p33-1
zimbra-proxy-components			->	1.0.10-1zimbra8.8b1
zimbra-php				->	7.4.27-1zimbra8.7b3
zimbra-httpd				->	2.4.53-1zimbra8.7b3
zimbra-apache-components		->	2.0.7-1zimbra8.8b1
zimbra-spell-components			->	2.0.8-1zimbra8.8b1
zimbra-nginx				->	1.20.0-1zimbra8.8b3
zimbra-common-core-jar			->	8.8.15.1658837424-1
zimbra-common-core-libs			->	8.8.15.1654854265-1
zimbra-mbox-conf			->	8.8.15.1568012813-1
zimbra-mbox-service			->	8.8.15.1568694943-1
zimbra-mbox-store-libs			->	8.8.15.1654854265-1
zimbra-mbox-war				->	8.8.15.1655458176-1
zimbra-mbox-admin-console-war	        ->	8.8.15.1653031987-1
zimbra-mbox-webclient-war		->	8.8.15.1658466576-1
zimbra-drive				->	1.0.13.1576152256-1
zimbra-timezone-data			->	2.0.1.1646993388-1
zimbra-openjdk				->	17.0.2-1zimbra8.8b1
zimbra-openjdk-cacerts			->	1.0.8-1zimbra8.7b1
zimbra-openssl				->	1.1.1q-1zimbra8.7b4
zimbra-cyrus-sasl			->	2.1.28-1zimbra8.7b3
zimbra-openldap-lib			->	2.4.59-1zimbra8.8b5
zimbra-openldap-client			->	2.4.59-1zimbra8.8b5
zimbra-openldap-server			->	2.4.59-1zimbra8.8b5
zimbra-ldap-components			->	1.0.18-1zimbra8.8b1
zimbra-core-components			->	2.0.18-1zimbra8.8b1
zimbra-postfix				->	3.6.1-1zimbra8.7b3
zimbra-postfix-logwatch			->	1.40.03-1zimbra8.7b1
zimbra-clamav				->	0.103.3-1zimbra8.8b3
zimbra-perl-mail-spamassassin	        ->	3.4.6-1zimbra8.8b3
zimbra-spamassassin-rules		->	1.0.0-1zimbra8.8b5
zimbra-openldap-server			->	2.4.59-1zimbra8.8b5
zimbra-chat				->	3.0.2.1655178187-1

NETWORK:

Package Name			           	Version
zimbra-patch				->	8.8.15.1658841204.p33-1
zimbra-mbox-ews-service			->	8.8.15.1657194582-1
zimbra-drive-ng				->	3.0.16.1637855904-1
zimbra-network-modules-ng		->	6.0.35.1657211057-1
zimbra-docs				->	3.0.8.1616090809-1
zimbra-connect				->	1.0.29.1635424238-1
zimbra-zco				->	8.8.15.1922.1658473938-1
zimbra-zimlet-auth			->	1.0.4.1652971904-1

ubuntu

Installing zimbra packages with system package upgrades

  • As root, check for updates so that the server checks the zimbra-patch patch repository for new packages:
apt-get update
  • Install the following packages on the Mailstore node:
apt-get install zimbra-common-core-jar zimbra-common-core-libs zimbra-mbox-store-libs
  • Then update the existing packages:
apt-get upgrade
  • Restart ZCS as the zimbra user:
su - zimbra
zmcontrol restart

Installing zimbra packages separately for NETWORK and FOSS

Upgrade OpenLDAP on the LDAP node

  • As root, install the package:
apt-get zimbra-ldap-apt-get install zimbra-ldap-patch
  • Restart ZCS as the zimbra user:
su - zimbra
zmcontrol restart

Install/Upgrade zimbra-proxy-patch on the Proxy node

  • As root, install the package
apt-get install zimbra-proxy-patch
  • Restart the proxy as the zimbra user:
su - zimbra
zmproxyctl restart
zmmemcachedctl restart

Install/Upgrade snmp on the Proxy node if installed

apt-get install zimbra-snmp-components
  • Restart the proxy as the zimbra user:
su - zimbra
zmproxyctl restart

Install/Upgrade zimbra-mta-components on the MTA node

  • As root, install the package
apt-get install zimbra-mta-components
  • If snmp is installed, upgrade the package before restarting the services:
apt-get install zimbra-snmp-components
  • Restart amavisd as the zimbra user:
su - zimbra
zmamavisdctl restart

Install/Upgrade zimbra-mta-patch on the MTA node

  • As root, install the package
apt-get install zimbra-mta-patch
  • If dnscache is installed, upgrade the package before restarting the services:
apt-get install zimbra-dnscache-components
  • Restart amavisd as the zimbra user:
su - zimbra
zmamavisdctl restart

Install/Upgrade zimbra-patch on the Mailstore node

  • As root, check for updates and install the package:
apt-get update
apt-get install zimbra-common-core-jar zimbra-common-core-libs zimbra-mbox-store-ibs
apt-get install zimbra-patch
  • If apache is installed, upgrade the package before restarting the services:
apt-get install zimbra-apache-components
  • If spell is installed, upgrade the package before restarting the services:
apt-get install zimbra-spell-components
  • If snmp is installed, upgrade the package before restarting the services:
apt-get install zimbra-snmp-components
  • Restart ZCS as the zimbra user:
su - zimbra
zmcontrol restart

Installing NG packages (NETWORK only)

Remove zimbra-talk on the Mailstore node

Starting with Zimbra 8.8.15 GA, the Talk package is superseded by zimbra-connect. Therefore, it is important to remove zimbra-talk before installing it . Replaced package: zimbra-talk by zimbra-connect

  • As root, remove the zimbra-talk package:
apt-get remove zimbra-talk

Install/Upgrade zimbra-network-modules-ng, zimbra-connect, zimbra-zimlet-auth, zimbra-docs and zimbra-drive-ng on the Mailstore node

  • As root, check for updates and install the packages:
apt-get update
apt-get install zimbra-network-modules-ng
apt-get install zimbra-connect
apt-get install zimbra-zimlet-auth
apt-get install zimbra-docs
apt-get install zimbra-drive-ng
  • Restart the Zimbra mailbox service as the zimbra user:
su - zimbra
zmmailboxdctl restart

Install/Upgrade zimbra-chat for FOSS

  • As root, install the package:
apt-get install zimbra-chat
  • Restart the Zimbra mailbox service as the zimbra user:
su - zimbra
zmmailboxdctl restart

Jira Summary

Jira Tickets Fixed in Joule 8.8.15 Patch 33

ZCS-11689Upgrade Zimbra OpenSSL to 1.1.1q
ZCS-11686Fixed purging of central volume blobs
ZCS-11682Fixed backup volume handler
ZCS-11681Improved error handling for the purge operation
ZCS-11680Skip backup of distribution lists and dynamic groups
ZCS-11679MustChangePassword was not evaluated for application credentials
ZCS-11569Fix missing XML declaration for EWS
ZCS-11567Remove the allowplugins option from Spamassassin's zmsaupdate script. (Ubuntu16)
ZCS-11406Fixed accounts folder when switching to external backup
ZCS-11302Classic UI – Users should not be allowed to use their username in the password
ZCS-11202RXSS on '/h/search' via 'Title' (8.8.15.p30)
ZCS-11200RXSS on '/h/search' via 'onload' (8.8.15.p30)
ZCS-11199RXSS on '/h/search' via 'Extra' (8.8.15.p30)
ZCOMT-2485ZCO sanity testing on Win 11 platforms
ZCOMT-2479During sync (intermittent), detect the old auto-complete cache and prompt the user with a Yes/No message to clear the old cache entries automatically.
ZCOMT-2475Investigate the issue of scheduling meetings with MS Teams through ZCO.
ZBUG-2901Denial of service (high CPU usage) caused by a regular expression even with zimbra_external_email_warning_enabled=false
ZBUG-2898Ubuntu 20, sed expression error
ZBUG-2865Authentication Bypass in MailboxImportServlet
ZBUG-2849/var/log/messages fills up after applying Zimbra 9 P25 (release 2)
ZBUG-2841Disable Syslog log shipping by default in Log4j V2.
ZBUG-2821Disable unwanted root sharing
ZBUG-2800Proxy Servlet SSRF Vulnerability
ZBUG-2676Upgrade Cyrus SASL to 2.1.28
ZBUG-2662When using preauth, CSRF tokens are not checked on some post endpoints.
ZBUG-2611Wrong default calendar when creating an appointment by double-clicking.
ZBUG-2546SendAs is not honored in ZCO
ZBUG-23732FA – Device not detected as Trusted in a ZCS multi-server environment

Kerim Koç

Systems and infrastructure engineer. I write about Linux, open source, high availability and security.