Skip to content

Upgrading

To move to a new release you run the new installation package the same way; your previous module selection is kept.

  1. Get the new package from Profelis and read the release notes.
  2. During a maintenance window, unpack the package and run it with the previous selection: 
    sudo ./install.sh --yes
  3. Verification should report PASS. Then hard-reload the admin console and webmail.

Zimbra patch package (zmpatch)

Profelis ships its own Zimbra PFE fixes as a separate patch package (zmpatch-…-ubuntuNN.tar.gz). The package is cumulative: it contains every patch from the base Zimbra installation up to today, so applying the latest package is enough. The included patches are listed in PATCHES.txt inside the package.

tar xzf zmpatch-…-ubuntu22.tar.gz
sudo ./zmpatch-…-ubuntu22/zmpatch-apply.sh --dry-run    # plan: same / replace / add
sudo ./zmpatch-…-ubuntu22/zmpatch-apply.sh
  • Files identical to the installed ones are skipped; changed files are backed up and replaced. If nothing changed it prints "already up to date" and mailboxd is not restarted.
  • An older package, or one missing a patch that is already installed, is refused; use --force to go back on purpose.
  • Installed package and patches: zmpatch-apply.sh --list. To undo: zmpatch-apply.sh --rollback <package>.
  • For Always On the package must include patch 604 (Zimbra PFE 10).
  • After a Zimbra version update run sudo ./install.sh --pre-zmsetup again so the swatch hardening is reapplied.
  • zmpatch 015 (swatch hardening) applies to both PFE 9 and PFE 10.

After a Zimbra version upgrade

Upgrading Zimbra itself renews some configuration templates and sign-in page files. Run the Profelis installation again with --yes afterwards; if you use the WAF, also run zimbra-guard-waf apply and restart mailboxd (see WAF setup).

User audit

User audit may come back switched off after some version changes. After upgrading, check that it is on under User Audit › Settings.