This was already the case in 8.7 IIRC.

Go through this thread, Frédéric released a script (and listed the bug related to the issue in last august).
http://lists.zetalliance.org/pipermail/ ... 01259.html

Hello.

Outdated doesn't mean broken/dangerous.
However, if you're afraid of that, you can do two things.
One is to firewall the access to the port.
The other is to update to 8.8.12P1, as PHP was upgraded in 8.8.12: https://wiki.zimbra.com/wiki/Zimbra_Releases/8.8.12

This is exactly the idea.

Welcome to the forum.

There's this: https://wiki.zimbra.com/wiki/Plus_Addressing

About issue #9, you might want to change the size of the redolog too so it gets deleted sooner and uses less space on disk. zmprov mcf zimbraRedoLogRolloverHardMaxFileSizeKB thesizeyouwant More info here: https://wiki.zimbra.com/wiki/Zimbra_NG_Modules/Running_Zimbra_NG_Modules_on_Zimbra_Network_Edit...

Looks like a "split domain" between two ZCS servers. That's not really "load balancing"...
IIRC, there's a page in the wiki about this.

Stop the services/VM. Put the VM in a "non routed" VLAN and/or use firewall to prevent users to be able to access them. Snapshot the VM. Restart the whole thing (as Zimbra needs to be running to upgrade) and check everything is ok (you'll need to have a workstation in the same non-routed V...

You might want to re-apply P3. They released it with an (unneeded) patch for Chrome (beta) that breaks Firefox. So they re-released it (the day after IIRC) with the fix, without changing its name (it's still P3, not P4 nor P3b). If you installed the first P3, you should re-download it and re-apply it.

And/or this work in progress: https://github.com/Zimbra-Community/zimbra-elasticstack