We are happy to announce a new patch release of CipherMail Webmail
Messenger. This release fixes a few bugs that could cause problems
while updating CipherMail appliances.
You are advised to create a backup before performing the update on any
production system. The full update procedure can be found here:
PLEASE NOTE: this time you are also advised to perform the update using
these three commands:
1. '$ sudo dnf clean metadata'
2. '$ sudo dnf update'
3. '$ sudo cm-run-playbook'
The first command ensures that our patched 'dnf-plugins-core' and
'mariadb' packages are available for installation, the second command
updates the packages, and the third command ensures that all
configuration gets applied. This *should* all happen automatically, but
there may be installations out there that are currently in an
inconsistent state due to bugs in previous versions of CipherMail
Webmail Messenger. We recommend running these commands just to be sure.
New virtual appliance images and package archives for offline
installation can be obtained through the support portal:
Customers with a CipherMail Webmail high-availability cluster are
advised to update their cluster one node at a time. More information
about cluster updates can be found on our documentation website:
CipherMail Webmail Messenger 4.2.2 release notes:
- Pin MariaDB to custom CipherMail version <= 3:10.3.32-2.1 because
MariaDB 3:10.3.32-2 breaks State Snapshot Transfers.
- Pin python3-dnf-plugin-post-transaction-actions to the
CipherMail-patched version of 4.0.21-4.1.el8. The Red Hat-provided
version contains a bug that prevented actions from running under
- Fixed an issue where an interrupted Ansible playbook did not result
in a warning in the administrative web interface.
- Prevent DNF from restoring the default MariaDB Galera configuration.
The default configuration conflicts with the CipherMail-provided
configuration, causing the service startup to fail.
IT Automation Engineer