Hi, first of all: Thanks ZEXTRAS for providing a new build! I am currently on ZEXTRAS_20231104 and what keeps me from updating is that I am not sure...

According tothis seems to be an NE-only feature. So FOSS might not be vulnerable?

This certainly looks like more than an average Cross-Site-Scripting thing... Maluda's Builds are also not available for P41 yet. Time to enter panic-m...

I am rather underwhelmed by CrowdSec. The block rules for Zimbra seem to be the same as fail2ban.It did not trigger any single event hit from the free...

Just did the update - worked without any problems. Thanks Zextras for your effort!

For backup: Before Zextras I did use Veeam Endpoint which did also trigger a pre-bash script (Basically zmcontrol stop) and a post-script (zmcontrol s...

The V10 build supply situation is too risky for me at the moment, so I will keep V9 for now. Also ZEXTRAS Suite is not available for V10, or?

Seems there is a new build available: zcs-9.0.0_ZEXTRAS_20231104.UBUNTU18_64.20231124122956Anyone tried it yet?

@kordian yet it still works in this particular case. Not saying it always works, in fact repo update broke my zimbra once in the past (glad I did a sn...

@kordian Just like in the quote. Ubuntu still has the official zimbra apt repositories unless you removed them.

@anahuac Went for a more brutal approach - deleted zimbra.log, zmcontrol restart, came back right away 😀 😀 😀 I guess you would not even have to res...

Have one minor issue after patching: Zimbra is no longer logging to /var/log/zimbra.log

Probably found the answer myself by comparing with dpkg -l | grep zimbra @anahuac Thank you again for sharing the steps!

@anahuac I can confirm that apt update apt upgrade /opt/zimbra/libexec/zmfixperms zmcontrol restart worked for me! Is there any way to veri...