Zimbra Build by Zextras - no Zextras support guaranteed - Zextras Forum

Zimbra 9.0 build by Zextras vulnerable to CVE-2025-48700 ?

cmbzextras — Thu, 04 Jun 2026 13:54:49 +0000

We're only some weeks from taking our new Carbonio system into production, now our Security Officer forwards us a mail from the Center for Cybersecurity Belgium with the message that our Zimbra system is found vulnerable to CVE-2025-48700. We currently run the 9.0.0_ZEXTRAS_20220713.FOSS build (and looking forward to take Carbonio into production). My question is whether this FOSS/Zextras build of Zimbra 9.0 is also vulnerable?
In previous similar sitations, e.g. in case of CVE-2024-45519, the Zimbra FOSS version was not affected, but I cannot find enough information about the CVE-2025-48700 and FOSS (Zextras) build to confirm/exclude for the current situtation. Can anyone help?
Thanks!

Download the old version of Zimbra9.0FOSS

asdwsx — Tue, 19 Aug 2025 04:42:29 +0000

How to download 9.0.0. ZEXTRAS. 20231104. UBUNTU20.64 UBUNTU20_64 FOSS

New Install Admin Console Not Working

kenwardc — Mon, 07 Apr 2025 13:06:00 +0000

Hi there Folks

I have been using Zextras with two mailservers for many years and today I created a brand new single server using the Zextras v9 build. All installed very well. I am able to login to the standard web client using the name "admin" because it's the only login so far but, if I try to go to the Admin Console the new tab doesn't open the Admin Console just eventually says timeout. I have tried using the IP address of the server with the :7071 port but it doesn't work at all.

I have disabled the IPTables and FirewallD and also disabled Fail2Ban so there is now no firewall sitting in front to stop traffic.

Please can someone help me with this? I need to get this new server running and get Zextras licences for it but cannot do that until it's working and I can use the Admin Console to create domains and accounts on the server.

Many thanks

Chris

Updating some packages (apt update && apt upgrade) break my zimbra server (started to get a "A network service error has occurred." when entering login page)

BetoCeni — Fri, 21 Mar 2025 15:53:14 +0000

Upgraded successfully from 8.8.15 to zcs-9.0.0_ZEXTRAS_20240927.UBUNTU20_64.20241001143114

Did all the steps on the documentation, including:

Fix the default globalconfig values by

zmprov modifyConfig zimbraMtaCommandDirectory /opt/zimbra/common/sbin
zmprov modifyConfig zimbraMtaDaemonDirectory /opt/zimbra/common/libexec
zmprov modifyConfig zimbraMtaMailqPath /opt/zimbra/common/sbin/mailq
zmprov modifyConfig zimbraMtaManpageDirectory /opt/zimbra/common/share/man
zmprov modifyConfig zimbraMtaNewaliasesPath /opt/zimbra/common/sbin/newaliases
zmprov modifyConfig zimbraMtaSendmailPath /opt/zimbra/common/sbin/sendmail

Disable DSPAM by

zmprov modifyServer `zmhostname` zimbraAmavisDSPAMEnabled FALSE
zmlocalconfig -e amavis_dspam_enabled=false
zmamavisdctl restart

Restarted zimbra services, checked the server, everything was fine.

So until this point I had a functional ZCS 9 from the 20240927 build.

Ran apt update, found the folloiwing packages available to be updated:

zimbra-mta-patch/unknown 9.0.0.1629795032.p18-1.u20 amd64 
zimbra-patch/unknown 9.0.0.1629795032.p18-1.u20 amd64 
zimbra-proxy-patch/unknown 9.0.0.1629795032.p18-1.u20 amd64

Updated these packages, restarted zimbra services, as documented. Checked services again, all services running. Checked zimbra.service with systemctl status zimbra.service....all green...

And now, when attempting to login to my mailbox I now get the "A network service error has occurred." Red error message.

Checked my mailbox.log, found:

at java.lang.Thread.run(Thread.java:833) 
Caused by: com.zimbra.common.service.ServiceException: error while proxying request to target server: Service Unavailable
at com.zimbra.common.service.ServiceException.PROXY_ERROR(ServiceException.java:409) ~

Reverted my snapshot prior to the update.

If someone could help me diagnose this, that would be terrific.

Mysql integrity errors

trigg3r — Sun, 09 Feb 2025 17:58:53 +0000

Zimbra Release 9.0.0.ZEXTRAS.20221203.UBUNTU18.64 UBUNTU18_64 FOSS edition.

I am applying this patch but the check on the mysql database returns the errors below. I managed to solve the errors on "chat." by deleting the related database, but the last 3 (Table 'mysql.gtid_slave_pos' 'mysql.innodb_index_stats' 'mysql.innodb_table_stats' doesn't exist in engine) I was not able to solve them even with Mysql Crash Recovery

Can you help me?

 /opt/zimbra/libexec/zmdbintegrityreport -v

Database errors found.
/opt/zimbra/common/bin/mysqlcheck --defaults-file=/opt/zimbra/conf/my.cnf -S /opt/zimbra/data/tmp/mysql/mysql.sock -A -C -s -u root --password=XXXXXXXX
chat.CHANNELV3
 Error    : Table 'chat.CHANNELV3' doesn't exist in engine
 chat.CONVERSATION_OPTIONS
 Error    : Table 'chat.CONVERSATION_OPTIONS' doesn't exist in engine
 chat.EVENTMESSAGE
 Error    : Table 'chat.EVENTMESSAGE' doesn't exist in engine
 chat.FIREBASE
 Error    : Table 'chat.FIREBASE' doesn't exist in engine
 chat.GROUP
 Error    : Table 'chat.GROUP' doesn't exist in engine
 chat.INSTANT_MEETING
 Error    : Table 'chat.INSTANT_MEETING' doesn't exist in engine
 chat.MESSAGE
 Error    : Table 'chat.MESSAGE' doesn't exist in engine
 chat.MESSAGE_READ
 Error    : Table 'chat.MESSAGE_READ' doesn't exist in engine
 chat.OWNER
 Error    : Table 'chat.OWNER' doesn't exist in engine
 chat.RELATIONSHIP
 Error    : Table 'chat.RELATIONSHIP' doesn't exist in engine
 chat.SPACE
 Error    : Table 'chat.SPACE' doesn't exist in engine
 chat.SUBSCRIPTION
 Error    : Table 'chat.SUBSCRIPTION' doesn't exist in engine
 chat.USER
 Error    : Table 'chat.USER' doesn't exist in engine
 chat.USERV3
 Error    : Table 'chat.USERV3' doesn't exist in engine
 chat.USER_ROOM_JOIN
 Error    : Table 'chat.USER_ROOM_JOIN' doesn't exist in engine
 chat.VISIBILITY
 Error    : Table 'chat.VISIBILITY' doesn't exist in engine
 mysql.gtid_slave_pos

 Error    : Table 'mysql.gtid_slave_pos' doesn't exist in engine
 mysql.innodb_index_stats
 Error    : Table 'mysql.innodb_index_stats' doesn't exist in engine
 mysql.innodb_table_stats
 Error    : Table 'mysql.innodb_table_stats' doesn't exist in engine

Long running SQL queries blocking mailboxes

btbs — Wed, 06 Nov 2024 11:42:36 +0000

Hi,

we have a problem with (mostly) one mailbox, that the user cannot retrieve mails/attachments and is unable to send mails or login via webinterface.
It took some time investigating, but apparently it comes down to this:

Every time when this happens, we see the mysql-process is using 100% of one CPU core and we see something like this query in the mysql processlist:

#> SHOW FULL PROCESSLIST;
Id      User    Host    db      Command Time    State   Info    Progress
6504    zimbra  localhost:44998 zimbra  Sleep   0               NULL    0.000
7479    zimbra  localhost:46622 zimbra  Sleep   2               NULL    0.000
28951   zimbra  localhost:41804 zimbra  Sleep   16              NULL    0.000
38392   zimbra  localhost:48888 zimbra  Query   1127    Sending data    SELECT COUNT(*) FROM mboxgroup20.mail_item AS mi WHERE mi.mailbox_id = 20 AND ((((mi.type = 0x05 OR mi.type = 0x06 OR mi.type = 0x10)) AND ((mi.id = 1013345) OR (mi.id = 1013349) OR (mi.id = 1013358) 
OR (mi.id = 1013375) OR (mi.id = 1013402) OR (mi.id = 1013412) OR (mi.id = 1013422) OR (mi.id = 1013438) OR (mi.id = 1013441) OR (mi.id = 1013444) OR (mi.id = 1013448) OR (mi.id = 1013455) OR (mi.id = 1013464) OR (mi.id = 1013466) OR (mi.id = 1013496) OR (mi.id = 1013512) OR (mi.id = 1013525) OR (mi.id = 1013531) OR (mi.id = 1013537) OR (mi.id = 1013555) OR (mi.id = 1013563) OR (mi.id = 1013565) OR (mi.id = 1013580) OR (mi.id = 1013585) OR (mi.id = 1013615) OR (mi.id = 1013624) OR (mi.id = 1013632) OR (mi.id = 1013638) OR (mi.id = 1013647) OR (mi.id = 1013651) OR (mi.id = 1013664) OR (mi.id = 1013677) OR (mi.id = 1013685) OR (mi.id = 1013687) OR (mi.id = 1013690) OR (mi.id = 1013725) OR (mi.id = 1013740) OR (mi.id = 1013750) OR (mi.id = 1013753) OR (mi.id = 1013760) OR (mi.id = 1013769) OR (mi.id = 1013799) OR (mi.id = 1013805) OR (mi.id = 1013812) OR (mi.id = 10138

Does anyone know, what this process does and why it is stuck in "sending data"? The query is huge, I cut it off in the excerpt above.

When I kill this process, everything seems to work fine after that.
The mailbox.log logfile then shows this error "imap - SEARCH failed":

2024-11-06 11:36:45,418 WARN    imap - SEARCH failed

This is rather frustating, I cannnot run around and kill mysql processes in order to work. The user is using an iPhone, but we already ditched that and set the mailaccount up on a new iPhone, it still shows up with this problem. So we can rule that out, it must have something to do with the server.

We are using Zimbra Release 9.0.0_ZEXTRAS_20240927.
The issue started over month ago. All other mailboxes seem to run fine.

Hope you can help me with this.

zimbra 9.0.0_zextras_20220713 new updates

sepladmin — Wed, 06 Nov 2024 11:30:50 +0000

Dear all,

presently we are using zimbra 9.0.0_zextras_20220713 below on our servers what is the latest version to upgrade

Issue during upgrade ZIMBRA 9 from zcs-9.0.0_ZEXTRAS_20231104 to zcs-9.0.0_ZEXTRAS_20240927

mlix — Mon, 28 Oct 2024 20:08:03 +0000

Hello,

I have issue during upgrade ZIMBRA 9 from zcs-9.0.0_ZEXTRAS_20231104 to zcs-9.0.0_ZEXTRAS_20240927.

Please about help or tips

Below are the installation logs

# ./install.sh

Operations logged to /tmp/install.log.QbwMGh24
Checking for existing installation...
zimbra-drive...FOUND zimbra-drive-1.0.14.1588924560-1
zimbra-imapd...FOUND zimbra-imapd-9.0.0_ZEXTRAS_20231104
zimbra-license-tools...NOT FOUND
zimbra-license-extension...NOT FOUND
zimbra-network-store...NOT FOUND
zimbra-network-modules-ng...NOT FOUND
zimbra-chat...FOUND zimbra-chat-4.0.3.1654677981-1
zimbra-connect...NOT FOUND
zimbra-talk...NOT FOUND
zimbra-ldap...FOUND zimbra-ldap-9.0.0_ZEXTRAS_20231104
zimbra-logger...FOUND zimbra-logger-9.0.0_ZEXTRAS_20231104
zimbra-mta...FOUND zimbra-mta-9.0.0_ZEXTRAS_20231104
zimbra-dnscache...FOUND zimbra-dnscache-9.0.0_ZEXTRAS_20231104
zimbra-snmp...FOUND zimbra-snmp-9.0.0_ZEXTRAS_20231104
zimbra-store...FOUND zimbra-store-9.0.0_ZEXTRAS_20231104
zimbra-apache...FOUND zimbra-apache-9.0.0_ZEXTRAS_20231104
zimbra-spell...FOUND zimbra-spell-9.0.0_ZEXTRAS_20231104
zimbra-convertd...NOT FOUND
zimbra-memcached...FOUND zimbra-memcached-1.4.37-2
zimbra-proxy...FOUND zimbra-proxy-9.0.0_ZEXTRAS_20231104
zimbra-archiving...NOT FOUND
zimbra-core...FOUND zimbra-core-9.0.0_ZEXTRAS_20231104
ZCS upgrade from 9.0.0 to 9.0.0 will be performed.
Validating ldap configuration
LDAP validation succeeded. Continuing.

----------------------------------------------------------------------
PLEASE READ THIS AGREEMENT CAREFULLY BEFORE USING THE SOFTWARE.
SYNACOR, INC. ("SYNACOR") WILL ONLY LICENSE THIS SOFTWARE TO YOU IF YOU
FIRST ACCEPT THE TERMS OF THIS AGREEMENT. BY DOWNLOADING OR INSTALLING
THE SOFTWARE, OR USING THE PRODUCT, YOU ARE CONSENTING TO BE BOUND BY
THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE TERMS OF THIS
AGREEMENT, THEN DO NOT DOWNLOAD, INSTALL OR USE THE PRODUCT.

License Terms for this Zimbra Collaboration Suite Software:
https://www.zimbra.com/license/zimbra-public-eula-2-6.html
----------------------------------------------------------------------

Do you agree with the terms of the software license agreement? Y

Checking current number of databases...

Do you want to verify message store database integrity? Y
Verifying integrity of message store databases. This may take a while.
mysqld is alive
No errors found

Use Zimbra's package repository N

Checking for installable packages

Found zimbra-core (local)
Found zimbra-ldap (local)
Found zimbra-logger (local)
Found zimbra-mta (local)
Found zimbra-dnscache (local)
Found zimbra-snmp (local)
Found zimbra-store (local)
Found zimbra-apache (local)
Found zimbra-spell (local)
Found zimbra-proxy (local)
Found zimbra-imapd (local)

The Zimbra Collaboration Server appears to already be installed.
It can be upgraded with no effect on existing accounts,
or the current installation can be completely removed prior
to installation for a clean install.

Do you wish to upgrade? Y

Scanning for any new or additional packages available for installation
Existing packages will be upgraded
Upgrading zimbra-core
Upgrading zimbra-ldap
Upgrading zimbra-logger
Upgrading zimbra-mta
Upgrading zimbra-dnscache
Upgrading zimbra-snmp
Upgrading zimbra-store
Upgrading zimbra-apache
Upgrading zimbra-spell
Upgrading zimbra-proxy
Upgrading zimbra-imapd
Upgrading zimbra-chat
Checking required space for zimbra-core
Checking space for zimbra-store
Checking required packages for zimbra-store
zimbra-store package check complete.

Installing:
zimbra-core
zimbra-ldap
zimbra-logger
zimbra-mta
zimbra-dnscache
zimbra-snmp
zimbra-store
zimbra-apache
zimbra-spell
zimbra-proxy
zimbra-imapd
zimbra-chat

The system will be modified. Continue? Y

Beginning Installation - see /tmp/install.log.QbwMGh24 for details...

zimbra-core-components is missing. ERROR
zimbra-timezone-data will be installed.
zimbra-common-core-libs will be installed.
zimbra-common-mbox-db will be installed.
zimbra-common-mbox-native-lib will be installed.
zimbra-common-core-jar will be installed.
zimbra-common-mbox-conf will be installed.
zimbra-common-mbox-conf-attrs will be installed.
zimbra-common-mbox-conf-msgs will be installed.
zimbra-common-mbox-conf-rights will be installed.
zimbra-common-mbox-docs will be installed.
zimbra-core will be installed.
zimbra-ldap-components is missing. ERROR
zimbra-ldap will be installed.
zimbra-logger will be installed.
zimbra-mta-components is missing. ERROR
zimbra-mta will be installed.
zimbra-dnscache-components is missing. ERROR
zimbra-dnscache will be installed.
zimbra-snmp-components is missing. ERROR
zimbra-snmp will be installed.
zimbra-store-components is missing. ERROR
zimbra-jetty-distribution is missing. ERROR
zimbra-mbox-store-libs will be installed.
zimbra-mbox-war will be installed.
zimbra-mbox-webclient-war will be installed.
zimbra-mbox-conf will be installed.
zimbra-mbox-service will be installed.
zimbra-mbox-admin-console-war will be installed.
zimbra-store will be installed.
zimbra-apache-components is missing. ERROR
zimbra-apache will be installed.
zimbra-spell-components is missing. ERROR
zimbra-spell will be installed.
zimbra-proxy-components is missing. ERROR
zimbra-memcached is missing. ERROR
zimbra-proxy will be installed.
zimbra-imapd will be installed.
zimbra-chat is missing. ERROR

Unable to find missing packages in repository. System is not modified.

p41 / CVE-2024-45519

mik — Wed, 02 Oct 2024 15:20:07 +0000

Hi Zextras-Team,

are there any plans to provide a build for Zimbra 9.0.0 P41.

There seems to be a highly critical vulnerability
Zimbra - Remote Command Execution (CVE-2024-45519), see: https://blog.projectdiscovery.io/zimbra-remote-code-execution/

Doed HAB work in Zimbra 9?

Lexus — Fri, 27 Sep 2024 12:36:30 +0000

Hello!

OS version: Ubuntu 20.04 fresh installation
Zimbra version: 9.0.0 by Zextras fresh installed just out-of-the-box

HAB (Hierarchy address book) can not be configured on fresh installed Zimbra.
Any command for zmprov HAB configuration return an error service.UNKNOWN_DOCUMENT for soap.

Results for executions:

ERROR: service.UNKNOWN_DOCUMENT (unknown document: HABOrgUnitRequest)

ERROR: service.UNKNOWN_DOCUMENT (unknown document: HABOrgUnitRequest)
com.zimbra.common.soap.SoapFaultException: unknown document: HABOrgUnitRequest
ExceptionId:qtp664457955-135:1727406672131:fe7fcaf0f0490ce7
Code:service.UNKNOWN_DOCUMENT
at com.zimbra.common.soap.Soap12Protocol.soapFault(Soap12Protocol.java:90)
at com.zimbra.common.soap.SoapTransport.extractBodyElement(SoapTransport.java:376)
at com.zimbra.common.soap.SoapTransport.parseSoapResponse(SoapTransport.java:349)
at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:341)
at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:196)
at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:189)
at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:447)
at com.zimbra.common.soap.SoapTransport.invokeWithoutSession(SoapTransport.java:432)
at com.zimbra.cs.account.soap.SoapProvisioning.invokeRequest(SoapProvisioning.java:624)
at com.zimbra.cs.account.soap.SoapProvisioning.invoke(SoapProvisioning.java:669)
at com.zimbra.cs.account.soap.SoapProvisioning.invokeJaxb(SoapProvisioning.java:728)
at com.zimbra.cs.account.soap.SoapProvisioning.createHabOrgUnit(SoapProvisioning.java:3123)
at com.zimbra.cs.account.ProvUtil.doCreateHabOrgUnit(ProvUtil.java:1771)
at com.zimbra.cs.account.ProvUtil.execute(ProvUtil.java:1615)
at com.zimbra.cs.account.ProvUtil.main(ProvUtil.java:4160)

========== SOAP SEND ==========

zimbra
2tdihvaK

===============================
======== SOAP RECEIVE =========

43199997
0_e428405c115c89a58753641813b79a6d1e71ca56_69643d33363a65306661666438392d313336302d313164392d383636312d3030306139356439386566323b6578703d31333a313732373434393837393530353b61646d696e3d313a313b747970653d363a7a696d6272613b753d313a613b7469643d31303a313835353731343332353b76657273696f6e3d32323a392e302e305f5a4558545241535f32303233313130343b

=============================== (227 msecs)
========== SOAP SEND ==========

0_e428405c115c89a58753641813b79a6d1e71ca56_69643d33363a65306661666438392d313336302d313164392d383636312d3030306139356439386566323b6578703d31333a313732373434393837393530353b61646d696e3d313a313b747970653d363a7a696d6272613b753d313a613b7469643d31303a313835353731343332353b76657273696f6e3d32323a392e302e305f5a4558545241535f32303233313130343b

fipa211.domain

===============================
======== SOAP RECEIVE =========

2a46c339-9f47-4aa2-89a4-df6383eab384
+com_zimbra_attachmail
+com_zimbra_phone
+com_zimbra_srchhighlighter
+com_zimbra_mailarchive
+com_zimbra_url
+com_zimbra_email
+com_zimbra_webex
+com_zextras_drive_open
+com_zimbra_ymemoticons
+com_zextras_chat_open
+com_zimbra_attachcontacts
+com_zimbra_date
(&(objectClass=inetOrgPerson)(objectClass=posixAccount)(uid=%u))
uid=zimbra,cn=sysaccounts,cn=etc,dc=fipa211,dc=domain
fipa211.domain
ldap://192.168.205.7:389
dcObject
organization
zimbraDomain
amavisAccount
cn=users,cn=accounts,dc=fipa211,dc=domain
5c25cdc4-0536-4be5-85cb-67ef444421f9
enabled
zimbra
ldap
fipa211.domain domain
active
Europe/Moscow
cc40aee4-7a16-4605-ae59-d8e10e5db910
20240925184208.863Z
local
20240925184208.859Z
woofwoofimasecretpasswordthatisreallydifficult
fipa211

=============================== (28 msecs)
========== SOAP SEND ==========

0_e428405c115c89a58753641813b79a6d1e71ca56_69643d33363a65306661666438392d313336302d313164392d383636312d3030306139356439386566323b6578703d31333a313732373434393837393530353b61646d696e3d313a313b747970653d363a7a696d6272613b753d313a613b7469643d31303a313835353731343332353b76657273696f6e3d32323a392e302e305f5a4558545241535f32303233313130343b

fipa211.domain

===============================
ERROR: service.UNKNOWN_DOCUMENT (unknown document: HABOrgUnitRequest)

127.0.0.1 - - "POST /service/admin/soap/AuthRequest HTTP/1.1" 200 603 "-" "zmprov 9.0.0_ZEXTRAS_20231104" 6
127.0.0.1 - - "POST /service/admin/soap/GetDomainRequest HTTP/1.1" 200 802 "-" "zmprov 9.0.0_ZEXTRAS_20231104" 2
127.0.0.1 - - "POST /service/admin/soap/HABOrgUnitRequest HTTP/1.1" 500 492 "-" "zmprov 9.0.0_ZEXTRAS_20231104" 3

createHABOrgUnit could be exectuted with -l ldap-provisioning, but HAB-groups configuration commands require SOAP and fail with same errors.

Does this zimbra build not support HUB?

or maybe i missed something in configuration or forgot some module to be installed?

Thank you!