Zimbra Forums

https://github.com/Zimbra/zm-jetty-conf/pull/24 Thanks. It would be really helpful if synacor could acknowledge the creation of a bug report in the forum thread where they pick it up from. It would have saved me the time recreating the issue and working out how to reproduce it. I assumed that nothi...

With HTTP Compression enabled, that same block of code gets generated like this Screenshot 2024-04-19 164354.png where you can see lines 968 and 997 - the start and end of the previously commented block are now simply single line self-closing comments, and the single line comment at 989 is perfectly...

This can be seen visually by looking at the generated /opt/zimbra/jetty_base/etc/jetty.xml file in Notepad++ Screenshot 2024-04-19 162759.png With HTTP Compression disabled, the xml file generator tries to comment out the entire HTTPCOMPRESSIONBEGIN to HTTPCOMPRESSIONEND block - lines 968-997. Howev...

Hi, The current advice is to disable HTTP Compression to mitigate BREACH attacks. In both zimbra 9 and 10, if you do this, it exposes a bug in the /opt/zimbra/jetty_base/etc/jetty.xml.in file that results in the server being unable to start due to malformed XML in the generated /opt/zimbra/jetty_bas...

Having tested all the alternatives, I am in no doubt that the only way to be successful in building/upgrading FOSS installations is to keep the basic build settings unaltered. So, PATCH_LEVEL must be left at GA. Adding anything further will sometimes break web client connectivity to the server, and ...

Though I am not currently building with Maluda's build system, the lessons learned are equally important for all FOSS builders. Having tested all the alternatives, I am in no doubt that the only way to be successful in building/upgrading FOSS installations is to keep the basic build settings unalter...

After a bunch of tests, it looks like the ONLY possibility for identifying unique builds in the GUI is the BUILD_NUMBER, which is back to where Adrian started. Note that even that number is checked during the installation, and the same base build (10.0.7) with an earlier build number will not instal...

Unfortunately, it looks like using an _ in the BuildReleaseCandidate breaks some stuff too. The upgrade ran through completely, but the web client will not accept connections. In the zmsetup log I see where it is updating the ServerVersion settings in ldap, and they are all being set to empty. Befor...

I was adding your changes when I noticed we have a patch version 8 incoming for release 10.0. That opens up the question of when do we build for FOSS? I would say we only make FOSS builds after the new patches have been published by Synacor for NETWORK - any earlier and we have a higher risk of get...

/home/git/zm-mailbox/build-common.xml:31: java.net.ConnectException: Connection timed out (Connection timed out) It shows you got a connection timeout when downloading the file https://repo1.maven.org/maven2/org/apache/ivy/ivy/2.3.0/ivy-2.3.0.jar Make sure you have connectivity from the build server...