Maldua's Zimbra FOSS Builds - Share your feedback

[JBravo]

I just upgraded 10.1.10 to the latest 10.1.15 and all seems to be OK

[yeak]

I have created a docker way to run Zimbra that I find it stable and easy to handle. It is using Maldua's Zimbra FOSS build. Try it and let me know.

https://github.com/mailhappen/zm-docker.git

Why docker?
1. Quickly roll out Zimbra and begin to use it already.
2. Save the hassle of OS setup, software dependencies and wrong configuration.

Please use a dedicated server to run Zimbra. The docker only helps you to start up Zimbra quickly.

[dfreddie]

Upgraded from 10.1.10p3 on Ubuntu 22.0.4.1 to 10.1.15 with no issues.

Thank you!!

[adrian.gibanel.btactic]

I have created a docker way to run Zimbra that I find it stable and easy to handle. It is using Maldua's Zimbra FOSS build. Try it and let me know.

https://github.com/mailhappen/zm-docker.git

Why docker?
1. Quickly roll out Zimbra and begin to use it already.
2. Save the hassle of OS setup, software dependencies and wrong configuration.

Please use a dedicated server to run Zimbra. The docker only helps you to start up Zimbra quickly.

Could you please create a new specific thread for your Mailhappen docker so that it does not get mixed up with Maldua's builds?

Once there I will make you some questions because I want to update Zimbra Foss Builders List wiki page properly.

Thank you.

[adrian.gibanel.btactic]

There have been some reported 10.1.15.p1 problems with zimbra-jetty-distribution package. Those seem to be related with CentOS 7 and maybe with Ubuntu 20.04 too.

CENTOS 7

We were not going to be releasing 10.1.15.p1 for CentOS 7 because it has been labeled as Deprecated by Zimbra since ZCS NE 10.1.10.

In addition to that jackpeter reported concerning issues back when 10.1.13 was released which hinted at some packages being updated in the CentOS 7 packages repo while some others were not properly updated there.

A recently created issue regarding CentOS 7 ended up with 10.1.15.p1 download under the Other category with a Deprecated warning.

So... yeah... I can understand why CentOS 7 wouldn't work properly.

UBUNTU 20.04

Question for Ace Suares:
Were you trying to update specifically from Maldua's 10.1.10.p3 version to Maldua's 10.1.15.p1 version ? Or did you try other FOSS vendor builds?

So Ubuntu 20.04 has not been labeled as Deprecated in the Zimbra NE downloads page but I think I have seen mentioned somewhere in the Release Notes that it was deprecated... or maybe Ubuntu 18.04 was the one I saw.

Anyways I cannot dig deeper for now. So, assuming this has been reported properly I suspect again on some packages being updated in the Ubuntu 20.04 packages repo while some others are not properly updated there.

I think we can safely discard an hypothetic commit embargo not being lifted problem because it would probably affect both Ubuntu 22.04 and Ubuntu 18.04.

Update on 2026-02-03

10.1.15.p1 does not have any problem with Ubuntu 20.04. This issue was caused by an apt-pinning left over.

Code: Select all

------------------------------------------------------------------------------------------
Date       | Username       | Platform         | From       | To         | Status | Note |
------------------------------------------------------------------------------------------
2026-01-18 | vchong68       | Ubuntu 22.04     | 10.1.10.p3 | 10.1.15.p1 | OK     | ()   |
2026-01-20 | omegainstitute | Ubuntu 22.04     | 10.1.9     | 10.1.15.p1 | OK     | ()   |
2026-01-23 | Skotsh         | Ubuntu 22.04     | 10.1.10.p3 | 10.1.15.p1 | OK     | ()   |
2026-01-31 | dgm            | CentOS 7         | 8.8.15     | 10.1.15.p1 | FAIL   | (1)  |
2026-02-01 | Ace Suares     | Ubuntu 20.04     | 10.1.10??? | 10.1.15??? | APT-PINNING ISSUE   | (2)  |
2026-02-01 | JBravo         | RHEL 8           | 10.1.10??? | 10.1.15.p1 | OK     | ()   |
2026-02-02 | dfreedie       | Ubuntu 22.04     | 10.1.10.p3 | 10.1.15.p1 | OK     | ()   |
------------------------------------------------------------------------------------------

I'll quote the different reported failures problems here for reference too.

(1):

Code: Select all

error: Failed dependencies:
        zimbra-jetty-distribution >= 9.4.57.v20241219-2.r7 is needed by zimbra-store-10.1.15_GA_4200001.RHEL7_64-20260123182817.x86_64

(2):

Code: Select all

Setting up zimbra-mbox-store-libs (10.1.15.1762779814-1.u20) ...
dpkg: dependency problems prevent configuration of zimbra-store:
 zimbra-store depends on zimbra-jetty-distribution (>= 9.4.57.v20241219-2.u20); however:
  Version of zimbra-jetty-distribution on system is 9.4.46.v20220331-2.u20.

[JBravo]

Sorry I didn't mention my platform. I'm using RHEL 8. Upgraded to 10.1.15p1

[adrian.gibanel.btactic]

Same here, on Ubuntu 20.04 and upgrading from 10.1.10

Code: Select all

Setting up zimbra-mbox-store-libs (10.1.15.1762779814-1.u20) ...
dpkg: dependency problems prevent configuration of zimbra-store:
 zimbra-store depends on zimbra-jetty-distribution (>= 9.4.57.v20241219-2.u20); however:
  Version of zimbra-jetty-distribution on system is 9.4.46.v20220331-2.u20.

I did

Code: Select all

apt install zimbra-jetty-distribution=9.4.57.v20241219-2.u20

and then install.sh again, but:

Code: Select all

Validating ldap configuration
connect: No such file or directory at bin/zmValidateLdap.pl line 159, <DATA> line 755.
Error: Unable to bind to the LDAP server as the root LDAP user.
       This is required to upgrade.

This is caused by an empty localconfig.xml. Which I always save before an upgrade so I copied that back and restarted install.sh.

Unfortunately, the installer removes the Jetty Distribution and installs the old version again.

Pinning helped:

Code: Select all

nano /etc/apt/preferences.d/zimbra-jetty

Package: zimbra-jetty-distribution
Pin: version 9.4.57.v20241219-2.u20
Pin-Priority: 1001

So... @Aces Suares after reading that you were able to install a newer version of zimbra-jetty-distribution it didn't make sense to me.

But now, let's take a look at:

Hi

I am on Maldua FOSS build system and used the binary for 10.1.4
after apt dist-upgrade today mailboxd and jetty dont work anymore.

I upgraded to 10.1.9 with Maldua binaries, Still not working.

My apt source where:

deb [arch=amd64] https://repo.zimbra.com/apt/87 focal zimbra
deb-src [arch=amd64] https://repo.zimbra.com/apt/87 focal zimbra
deb [arch=amd64] https://repo.zimbra.com/apt/1000 focal zimbra
deb [arch=amd64] https://repo.zimbra.com/apt/1010 focal zimbra

I changed it to

deb [arch=amd64] https://repo.zimbra.com/apt/87 focal zimbra
deb-src [arch=amd64] https://repo.zimbra.com/apt/87 focal zimbra
deb [arch=amd64] https://repo.zimbra.com/apt/1000 focal zimbra
#deb [arch=amd64] https://repo.zimbra.com/apt/1010 focal zimbra
deb [arch=amd64] https://repo.zimbra.com/apt/10.1.9 focal zimbra

Then i installed an older jetty version
apt update
apt install zimbra-jetty-distribution=9.4.46.v20220331-2.u20

Then I pinned it
cat /etc/apt/preferences.d/zimbra-jetty-pin
Package: zimbra-jetty-distribution
Pin: version 9.4.46.v20220331-2.u20
Pin-Priority: 1001

And now it works again. Took me a couple of hourse though.

Ace

So... the reason why you weren't able to upgrade properly to 10.1.15.p1 is because you had an apt-pinning left over.

You were specifically forcing your system to use an older version of zimbra-jetty-distribution package even if a newer one was available. 10.1.15.p1 was expecting to find the latest one.

In order words, you would have avoided all of the issues probably including localconfig.xml issue if you hadn't had that extra apt-pinning.

You should not expect that a workaround for one specific version it's going to work forever (and not cause issues for future versions).

Please make sure to delete both:

Code: Select all

/etc/apt/preferences.d/zimbra-jetty-pin
/etc/apt/preferences.d/zimbra-jetty

files and run:

Code: Select all

apt update

so that it does not mess up any more with your system.

Additional note: Hopefully the installer has also reverted your manual zimbra.list edits because this change you made:

Code: Select all

#deb     [arch=amd64] https://repo.zimbra.com/apt/1010 focal zimbra
deb [arch=amd64] https://repo.zimbra.com/apt/10.1.9 focal zimbra

only can break stuff.

So... the moral of the history for everyone here is that you need to know why you do things and document each one of your unexpected changes so that you can revert them when needed.

[Ace Suares]

Thanks for taking time to answer!

I can agree only that it's a messy process since Zimbra stopped giving out builds. I did Maldua and Zextras I think, so there is some confusion. I did stupid things like doing -s at install.sh. But in general, after a bit of tossing around, this one is working again. What I didn't mention is that I had to comment out DocServer in jetty.xml.in and also added a full path to runuser in the init.d script, apparently runuser is not in the cron path so I need to replace runuser with /usr/sbin/runuser or whatever the path is.

I am very grateful for these builds, is what I want to let you know.

[jered]

I just upgraded on RHEL 8 from Ian's Q3 build to the Maldua 10.1.15p1 (sorry, Ian) because of the endless critical embargoed patch issue with Zimbra upstream.

I ran into two problems:
1) I had to undo my "dnf versionlock" on zimbra-jetty-distribution (which was to work around a different Zimbra screwup)
2) I had to manually downgrade zimbra-timezone-data from the version in packages, because the revision number was lower in the Maldua build

So far, so good....

[Ace Suares]

On another Ubuntu 20.04 server I first did a release upgrade to 22.04, then tried to install 10.1.15. There where no dependency errors, but the installer could not login as root to ldap for some reason. I had to edit the root password of ldap and didn't know how to do that until i found my own post: viewtopic.php?t=68882
After that, the upgrade went smooth!