2034 SP 2 (2.4.87582)

Preparation

• A snapshot / backup of the appliance should be taken before starting the update

Important

• Please make sure you install the latest versions of REDDOXX Desktop and the REDDOXX Outlook AddIn so that post archiving and access to the REDDOXX MailDepot works correctly.
• The notifications of the virus scanner have been completely revised and will be reset to default settings during the update. Please make a note of the settings before the update and adjust them again after the update (Spamfinder => Filter Settings => Virus Scanner).
• Unfortunately, an update under Microsoft Azure is currently not possible and is therefore blocked. This functionality will be added later.

New features

• A diagnostic message is displayed if Freshclam cannot update
• The compliance log now contains the name and description of the audit
• The Indexer Service is monitored as a process
• A full text search is now possible in the log files
• The search in the virus quarantine is applied to all fields
• The trust status of collected root S/MIME certificates can be changed manually
• Auto Create Users can be activated for Reddcrypt organizations
• In HyperV environments, you can select during installation whether components required for Azure operation should be activated
• An independent TLS configuration can be made in the POP3 Connector, e.g. to be able to retrieve journal mails from 2013 Exchange servers again
• The security level (CipherSuites used) is now dynamically adjusted depending on the TLS versions used.

Bugfixes

• userlookupQuery for Notes Realm {uid=(0)} can be used again
• Exceptions for Auto Whitelist Adjustment are taken into account again
• The license report is now sent to the specified email address instead of the admin address
• The extended search for date and time in the user interface is now carried out correctly
• Paging for CISS domain selection and user assignment is applied correctly and is no longer limited to 25 results
• Archiviung via Outlook Addin now correctly sets the access rights again
• Expired AWL entries are updated if the CISS challenge is answered correctly
• Umlauts and special characters in specially formatted emails are displayed correctly in the user interface
• The appliance search in the admin web interface now shows the correct panels
• Both versions (encrypted and decrypted version) of emails can be saved again in the user interface if they have been processed by MailSealer

Hotfixes

The following problems with this service pack and related hotfixes or workarounds are known.
You can install the respective hotfixes in the Admin Webinterface => Administration => Updates => Install hotfixes.
Obsolete hotfixes in the table are integrated into more recent hotfixes and are therefore no longer available.

Hotfix Details

Detailed descriptions are provided below for the existing hotfixes.

19-memdiag-cleanup

In the hotfix the logrotate was optimized and prevents a constant increase of the data partition.
The memory diagnosis has been revised and provides more detailed information in the event of a memory error.

18-manitu

The hotfix checks whether the ix.dnsbl.manitu.net RBL is in use and sends a notification to the configured Appliance Administrator.
The RBL ix.dnsbl.manitu.net must be removed from the configuration of the SMTP Receive Connector .

17-haproxy-start

With very slow appliances (boot time of several minutes) it can happen that the web server is not accessible after the boot, this has been optimized with the hotfix

16-fuzzy-daemon

The hotfix updates the pattern based spam filter

15-mailsealer

The hotfix fixes a potential problem where certain E-Mails could not be decrypted correctly.

14-md-systemmgr-ssh

The hotfix fixes the following problems:

• SSH service restart so that the hotfix 12 is activated correctly
• Fixed display problem in MailDepot for encrypted emails
• Selection error for storages in MailDepot corrected

13-august24

The hotfix fixes several problems:

• DKIM signatures, if configured, are now correctly added only to outgoing emails
• With over 25 realms, paging is applied correctly in the corresponding views
• A calculation error in the license report has been fixed
• The MailSealer option "Bounce mail if invalid signature" now works correctly again

12-ssh

The hotfix closes the OpenSSH RegreSSHion vulnerability.

10-freshclam

Due to a bug in ClamAV, parts of the patterns could not be updated, this will be corrected with the hotfix.

09-logrotate

Unfortunately, the logrotate did not take the MongoDB log files into account, this has been corrected.

08-notification

• The hotfix notification was defective, this has been corrected

07-service-restart

• The hotfix solves the problem that sometimes the remote support service could not be restarted correctly
• In addition, a configured Samba share (Configuration => Network => SMB/CIFS) can now be accessed again via the eth1 interface

06-console-refresh

• The serial number was sometimes not displayed in the appliance console and the status of installed hotfixes was incomplete

05-hwdetection-azure

• Adjustment of hardware detection on Azure appliances for update compatibility

04-hwdetection-azure

• Adjustment of hardware detection on Azure appliances for update compatibility

03-maintenance

• The maintenance mode that can be activated in the admin web interface preserves the state even if a reboot or update is done

02-freshclam-notify

• The appliance sent virus pattern warnings even when no virus scanner was active, this has been corrected.

01-timediag

• The "Network Time" diagnose had issues when using the check time drift option, this has been fixed

Known problems

• The update may not be able to be carried out due to a lack of support for the CPU flag "avx"
  We have provided a FAQ for this.

• The UPN sync currently fails (UserPrincipalName must not be null), so please use a customized User Object filter in the realm as a workaround:

  (&(objectClass=user)(objectCategory=person)(userPrincipalName=*))

• NFS storages that are located on a QNAP may only be opened after the update if the NFS version is set to v3
  (in the Admin web interface => Configuration => Storages => Double-click on NFS Storage)