ZCP 7.2.2 beta 1 is available!

February 10, 2016 by Suyi  

We are glad to announce the immediate availability of ZCP 7.2.2 beta 1. Please read this announcement carefully as there are some points that needs to be taken into account before upgrading to ZCP 7.2.2 beta 1.

With this release we introduce some major key feature enhancements, such as the direct support for systemd and the support for native IPv6 sockets. Additionally, we have included many upstream-related fixes which allow the operation of ZCP on a broad range of modern systems.

These changes require some changes to existing configuration files which are not (in respect on special setups) updated automatically and require attention with upgrading:

  • Most daemons are now started using an unprivileged user. Be sure that "run_as_user" and "run_as_group" are commented out to use the default, "zarafa". If using our prebuilt DEB/RPM packages, this user and group will be created on installation (if not already present).
  • To facilitate use of IPv6 on a single socket, zarafa-dagent no longer binds to the IPv4-only by default. It is advised to review your firewall settings and perhaps block port 2003 if applicable.
  • Default socket locations have changed to /var/run/zarafad. Please review your /etc/zarafa/*.cfg and other configuration files (e.g. WebApp & Z-Push) for the server socket parameters after installation to make sure they are consistent.
  • In case of Multi-Server environments not using network-based socket configurations please check the LDAP tree for the zarafaFilePath attribute of Zarafa Server objects.
  • Default PID file locations have changed to /var/run/zarafad. Check for duplicate programs running on non-systemd services.

So please plan in a small amount of time to adjust existing /etc/zarafa/*.cfg files, as these changes are required for operation. You can always consult the example files shipped with installation, like for example with the *.rpmnew files installed in parallel.

Required config changes at a glance

The following configuration file parameters have received changes:

  • In the files admin.cfg, backup.cfg, dagent.cfg, gateway.cfg, ical.cfg, licensed.cfg, monitor.cfg, search.cfg, spooler.cfg
    • Change the parameters: server_socket, run_as_user, run_as_group
  • In the files: dagent.cfg, gateway.cfg, ical.cfg, licensed.cfg, monitor.cfg, search.cfg, server.cfg, spooler.cfg
    • Change the parameter: pid_file
  • In the file: server.cfg:
    • Change the parameters: server_pipe_name, server_pipe_priority, search_socket, license_socket, run_as_user, run_as_group
  • When using WebApp or WebAccess on the same server as ZCP, also change the file: config.php
    • Change the value at: define('DEFAULT_SERVER')
  • When using Z-Push on the same server as ZCP, also change: backend/zarafa/config.php
    • Change the value at: define('MAPI_SERVER')

Please make sure these parameters are changed accordingly to reflect the new /var/run/zarafad subdirectory for PID files and sockets. Any (custom) scripts running on the local ZCP server may also be affected by this change.

The path towards final

As usual, every release of ZCP includes many fixes in terms of stability, which will also be included into the next release. With ZCP 7.2.2 we will introduce Zarafa Backup Plus which is the successor to our existing Zarafa Backup introducing great new features - more details on Zarafa Backup Plus will be made available with the Release of ZCP 7.2.2 beta 2. We additionally intend to provide some smaller improvements like support for ECDHE which allows perfect forward secrecy (PFS).

Got feedback?

We are always interested in your feedback! Contact our support team or drop your feedback on the forum!