Zimbra Forums

Here is what I ended up doing after looking at build.pl and seeing how they were appending BUILD_RELEASE_CANDIDATE at line 323. EchoToFile( "$GLOBAL_PATH_TO_SCRIPT_DIR/RE/MICRO", "${MICRO}_$CFG{BUILD_RELEASE_CANDIDATE}" ); By adding the newest patch level from your tags list and ...

It is horrible... It will happen to me at least a few times every day and almost always when I am in the middle of composing a post to these forums and using preview to proof read. If feels like a security appliance that is acting up on their end. I can have a 502 on one browser window and move over...

Thanks for the suggestions and I will investigate. One thing I noticed on my builds that failed had to do with build.pl --build-release-no=${ZM_BUILD_RELEASE_NO} ... They have checking on this field so that 10.0.7 will work but 8.8.15.P1 will fail as a regex will catch that it's not 3 dot separated ...

This is really nice work! I created a simple bash script and built the latest builds using tags for version 8, version 9, and version 10. These are built using the tag list created by your zimbra-tag-helper tools I saw this project is using. I copied zm-build-filter-tags-9.sh and renamed it zm-build...

Is that automated list an output from maldua's zimbra-tag-helper? It was. My memory is really hazy on what I did as I didn't save my failed build script. It was early in my exploration of building from tags from your discussion with Ian on the possibility of building FOSS releases this way. I found...

Jim, The instructions in zm-build list the build tags as --git-default-tag=10.0.6,10.0.5,10.0.4,10.0.3,10.0.2,10.0.1,10.0.0-GA Your script will miss the 10.0.0-GA tag I believe, and if you look back at the zimbra 9 build tags there are some extra surprises like .... 9.0.0.p33,9.0.0.p32.1,9.0.0.p32 ...

Just visit https://wiki.zimbra.com/wiki/Zimbra_Releases to find out what is the latest tagged release, after just go to zm-build and zm-network-build repos and find out the latest tags published, and use all this information to create a build. We don't create patch tags in a repo if it doesn't cont...

nginx 1.24 as delivered with 10.0.0 P7 and 9.0.0 P39 is now using extended capabilities much like ldap does so it can run as non root and bind to a port below 1024. You can see this addition in zmfixperm. % getcap /opt/zimbra/common/sbin/nginx /opt/zimbra/common/sbin/nginx cap_net_bind_service=ep He...

Given that you have already tried zmfixperms which does a setcap so that non root can bind to sockets below 1024, I would investigate the file system and if it supports extended capabilities. % su - # tune2fs -l /dev/sda | grep "Filesystem features" Filesystem features: has_journal ext_att...

You are correct and thanks for sharing. Another option without whitelisting is to replace that generic rule with 2 rules. Example shown below if your WAF is doing something similar. #========================================================================= # BEGIN Zimbra client says it is sending so...