We are happy to announce a new patch release of CipherMail Webmail
Messenger. It contains only small, targeted fixes and we encourage
everyone to update their systems as soon as it is convenient. This
release fixes a few bugs related to the retrieval of Office 365 IP
ranges, an issue that could cause outbound SMTP connection problems on
IPv4-only systems, and an error that could occur when saving mailbox
auto-expunge configuration.
You are advised to create a backup before performing the update on any
production system. The full update procedure can be found here:
https://www.ciphermail.com/documentation/virtual-appliance-guide/minor-upda…
You can update your CipherMail Webmail installations using the
CipherMail Console menu, or with '$ sudo dnf update' on the command
line. New virtual appliance images and package archives for offline
installation can be obtained through the support portal:
https://support.ciphermail.com/user/downloads
Customers with a CipherMail Gateway 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:
https://www.ciphermail.com/documentation/cluster-administration-guide/clust…
CipherMail Webmail Messenger 4.1.4 release notes:
**Bug fixes**
- Microsoft recently shut down the Office 365 cloud components in
Germany. This caused HTTP 400 errors to occur in the CipherMail web
service client that obtained the Office 365 IP ranges through a
Microsoft-provided API. This release removes the German API endpoint
configuration from the web service client.
- On IPv4-only hosts, the Postfix MTA would in some cases attempt
outbound connections over IPv6. These connection attempts would be
put in caches and logs, which made it harder to troubleshoot
connection problems.
- An error would occur when saving the mailbox expunge configuration.
The script responsible for this action erroneously tried to save the
configuration in the (old, no longer existing)
/etc/ciphermail-webmail directory. In this release, the expunge
configuration file is stored in /etc/ciphermail instead.
--
Imre Jonk
System Administrator
CipherMail B.V.
We are happy to announce a new patch release of CipherMail Email
Encryption Gateway. It contains only small, targeted fixes and we
encourage everyone to update their systems as soon as it is
convenient. This release fixes a few bugs related to the retrieval of
Office 365 IP ranges and an issue that could cause outbound SMTP
connection problems on IPv4-only systems.
Users of the Community Edition can find new distribution packages
here: https://www.ciphermail.com/downloads-gateway-distributions.html
Virtual appliance images are also available for download:
https://www.ciphermail.com/downloads-virtual-appliance.html
You are advised to create a backup before performing the update on any
production system. The full update procedure can be found here:
https://www.ciphermail.com/documentation/virtual-appliance-guide/minor-upda…
Customers with an active subscription can update their CipherMail
Gateway installations using the CipherMail Console menu, or with
'$ sudo dnf update' on the command line. New virtual appliance images
and package archives for offline installation can be obtained through
the support portal: https://support.ciphermail.com/user/downloads
Customers with a CipherMail Gateway 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:
https://www.ciphermail.com/documentation/cluster-administration-guide/clust…
CipherMail Email Encryption Gateway 5.1.4 release notes:
**Bug fixes**
- Microsoft recently shut down the Office 365 cloud components in
Germany. This caused HTTP 400 errors to occur in the CipherMail web
service client that obtained the Office 365 IP ranges through a
Microsoft-provided API. This release removes the German API endpoint
configuration from the web service client.
- On IPv4-only hosts, the Postfix MTA would in some cases attempt
outbound connections over IPv6. These connection attempts would be
put in caches and logs, which made it harder to troubleshoot
connection problems.
--
Imre Jonk
System Administrator
CipherMail B.V.
