Installation Notes

Auto Reboot

A new kernel is going to be installed and a reboot of the system is necessary. The output of the installation can be disrupted before the reboot is initialized.

Note: Please wait, until all software packages are installed. The reboot of the system will then be initialized automatically and the server is going to be available after a few minutes.

New in this Version

E-Mail: Alternative SMTP Server Name Setting

If an MX record exists for a Collax SMTP server, a valid DNS host name is required for the server. Previously, the host name for the Collax SMTP server was identical to its own FQDN. To enable more flexible settings for the internal infrastructure or for the external SMTP communication, it is now possible to specify an alternative SMTP server name.

Backup/Restore: New Version of the Backup Software Bacula

This update updates the backup software of the Collax servers to version 5.0.3.

Note: Within a Collax backup server/client environment, all involved server or clients should be updated to the latest version.

Collax Net Backup: New Version of the Central Backup Software Bacula

This update updates the central network backup software to version 5.0.3. We recommend installing the latest software package and reloading the configuration file on connected backup clients (Windows clients).

Misc: Zarafa 6.40.2

With this Collax software update the new version 6.40.2 of Zarafa Groupware is available. The upgrade to the version 6.40 can be initiated after the installation of Collax update 5.0.20 in the dialog Settings -> Mail and Messaging -> Zarafa Groupware -> Configuration, Tab Upgrade. This version mainly includes improvements and some new funcionality for Zarafa Webaccess. Please find details here:

https://doc.zarafa.com

Misc: Zarafa 6.30.16

This update provides the new version 6.30.16 of the Zarafa Groupware. This version mainly contains improvements and some new features for Zarafa WebAccess. Check here for details:

https://doc.zarafa.com

Misc: Backup Targets for Zarafa Bricklebel Backup

Zarafa Bricklevel Backup enables backup and restore of individual groupware objects at user level. Previously, the backup data were written to the local hard-disk area. As of this update, it is possible to specify other backup targets from the Collax backup. This includes SMB shares and NFS directories in the network.

Misc: Configurable Zarafa Auto-Reply Interval

As of this update, the auto-reply interval can be configured globally. The previous default interval of 24 hours can now be adjusted. Additionally, it is possible to specify whether the auto-reply is to be sent to the sender in the case of CC or mailing list e-mail.

Misc: Flexible Settings for Zarafa Bricklevel Backup

As of this update, the settings concerning the backup interval, the incremental backup interval, and the retention period can be configured individually.

Misc: Grace Period for License Exceeding

As of this update, a grace period of 4 weeks is granted if license limits are exceeded. Previously, it was not possible to activate configurations via the Web administration when the license limit was overstepped. This is now possible within the grace period. The grace period applies exclusively to the permissions in the dialog System -> System Operation -> Software -> Licenses and Modules, thereby facilitating the hardware migration of a server. Information on the remaining grace period is displayed in the Web administration. Overstepping of the runtime is not permitted; the restriction for system updates remains.

Issues Fixed in this Version

E-Mail: Size Limit Not Identical for Incoming and Outgoing E-Mail

If the e-mail size limit was changed for outgoing e-mail, this value was not automatically set for the fetchmail process. This has been corrected with this update.

Certificates: CSR and Certificates Signed by Official CA

Previously, the import of certificates signed by an official CA did not work, as the signature by the official CA changes the value of the subject. This issue has been corrected with this update. Certificates signed by an official CA can now be imported.

Fax: Size of Fax (TIFF) Stored to Share 0 Bytes

Fax messages stored as TIFF had a size of 0 bytes. On the Collax server itself, the fax messages were stored in the correct size. This error has been corrected with this update. Fax messages are now stored to a share in the correct size in TIFF image format.

Backup/Restore: Backup to SMB Share Includes IMAP Folder Admin.Virus

Previously, the backup element “Mailboxes” also contained administrative folders like Admin.Virus or Admin.Spam, which is used for storing virus-infected incoming e-mail for review by the administrator. This caused problems when the mailboxes including the Admin.Virus folder were stored as data backup to a SMB share monitored by a virus scanner. As of this update, the administrative folders are separated from the backup element “Mailboxes”.

Collax E-Mail Archive: E-Mail from a CD/DVD Exported from a Windows PC Is Not Loaded

Archive volumes written to ROM media can be provided for the archive search via a Windows share for the Collax e-mail archive in the network. The export of the archive from Windows systems is faulty in some cases, as the files end with a dot, which, however, is not exported by Windows. This update solves this problem, enabling the Collax e-mail archive to load incorrectly exported files, making them available for the archive search.

Collax E-Mail Archive: Archive Status Not Displayed

Volumes created by the e-mail archive have a certain status that can be viewed in the archive status dialog. If there were many archive volumes, the dialog could not be viewed. This update corrects the display, enabling the status of the archive volumes to be viewed.

Collax E-Mail Archive: Indexing of Archive Volumes

The indexing of e-mail in an archive volume is performed once a day. When a new archive volume was created between two indexing cycles, filled with incoming and outgoing e-mail in the specified size, and subsequently closed, it was previously impossible to index this archive volume. This update corrects the indexing for this case.

Misc: Collax Backup of Zarafa E-Mail Attachments Includes Zarafa Bricklevel Backup

Files

Stored Zarafa Groupware attachments can easily be backed up with Collax backup. When backing up attachments, individual elements from Zarafa Bricklevel Backup were also backed up, which slightly increased the hard-disk space occupied on the target system. As of this update, Zarafa attachments and Zarafa Bricklevel Backup data can be administered by means of separate backup jobs.

Misc: Dynamic DNS Does Not Work with DHCP (Cable Modem)

The objective of dynamic DNS is to address hosts with dynamic IP addresses over a fixed name. When DynDNS was selected with the connection type DHCP (cable modem), an empty configuration file was generated, and the DynDNS name of the server could not be updated. This issue has been corrected with this update.

Security: Read Access to Collax Web Access File Lists without Authentication

Previously, the system directory of the Collax Web access could be accessed without authentication in a browser. The form, CSS, and image directories of the Web access were listed, and it was possible to view the files. As of this update, the Collax Web Server denies read access to this directory.

Notes

Add-on Software: New Licensing of Avira Antivir

The Anti Virus product Avira Antivir will now be identically licensed as all Collax Modules. With this method a higher handling comfort is reached and the separate Avira Antivir-License integration is now redundant. Updating the license manually will not be necessary anymore.

Add-on Software: Download Progress Bar when using Avira Antivir Web-Virus-Filter

The anti virus product Avira Antivir displayed a special progress bar while scanning downloaded files. With the new anti virus technology within this update this progress bar becomes superfluous. From this update the progress bar of Avira Antivir is going to be removed.

Misc: PHP update 5.3.6

In cause of the major-release of PHP 5.3.6 it is possible that files which use PHP have to be adapted.