We will be releasing Baruwa Enterprise Edition version 2.0.6 on Monday 27th October 2014

This is an important update as it includes updates to critical dependencies with changes to various configuration files.

The puppet configurations have been cleaned up moving most files into the packages to decrease the complexity of configuration.

This post introduces the changes and allows you to prepare for the upgrade.

Important changes

Baruwa

This is a bug fix and enhancement update which takes the version to 2.0.6. The changes are as follows.

Bug fixes

• FIX: Prevent normal users from previewing messages that are dangerous.
• FIX: Support new domain names such as .system.
• FIX: Improve email and domain name validation.
• FIX: Improve the previewing of messages with lots of embedded CSS.
• FIX: Possible XSS in Message Preview.
• FIX: Unicode decoding errors in Message Preview.
• FIX: Active Directory LDAP lookups failing when there are referrals.
• FIX: Incorrect MailScanner SQL configuration options being loaded.
• FIX: Domain actions were not displayed in domain search results.
• FIX: Disable weekly, daily reports for users in cron as they are not supported.
• FIX: Fixed the Fanout router naming.
• FIX: Ensure indexer is installed for updatedelta.
• FIX: Bug #49 Confirmation text longer than field.
• FIX: Fixed issue with corrupt PDF reports.

New Features

• Added a REST based OAUTH authenticated API
• Moved MailScanner rulesets to file based rulesets, SQL rulesets were not scaling well for very large installations.
• Added support for After SMTP Anti-Virus Checks, This per domain setting allows AV checks to be ran after accepting the message to allow for actions to be applied such as Delete, Deliver, Quarantine.
• Added support for setting default language and setting the languages available for translation. This allows users to limit languages to only those they can support.
• Added support for setting spam and high spam scores and actions on outbound relays. This setting only works on outbound relays that have an IP address specified.
• Added support for Virus infected actions allowing for deliver, delete and quarantine of Virus infected messages.
• Added cache control support.
• Added the cleanup of the AWL database table.
• Improved the documentation especially the manual configuration section.
• Added the API documentation.
• Updated translations.

MailScanner

Bug fixes

• FIX: Fixed the permissions on the quarantine directory.
• FIX: Implemented locking for the phishing data scripts, to prevent multiple instances running.
• FIX: Esets wrapper binaries location corrected to allow out of the box functionality.
• FIX: Duplicated headers issue causing messages to get rejected by some mail servers specifically Yahoo with the error message Headers are not RFC compliant.
• FIX: Minor code cleanup

New Features

• Improvements to the default configuration, align default configuration with Baruwa functionality.
• Moved rulesets from puppet into rpm package to reduce the number of templates setup by puppet.
• Added the file wrapper command to the rpm package.
• Package now creates the inbound and outbound Exim queue directories.
• Added German rule updates to the rpm package.
• Implemented Exim queue cleanup scripts, this cleans stale queue files in the queue directories.
• Added KAM rule updates.
• Added SEM DNSBL checks
• Added SA Banks phishing plugin
• Added Baruwa DNSBL checks

Repoze.plugin.ldap

Bug fixes

• FIX: LDAP authentication failed when connecting to Active Directory servers which have referals enabled.

Exim

Exim has been upgraded to version 4.84.

New Features

• Moved most of the puppet templates into the rpm package.
• Proxy support now included allowing Baruwa to function correctly behind load balancers using the Proxy Protocol.
• New command-line option -C for exiqgrep to specify alternate exim.conf file when searching the queue.
• PRDR support now included.
• Moved to GNUTLS builds dropping OpenSSL support.

Updated packages

Updated Enterprise Edition packages are available from the Enterprise repository. The packages will hit the repository on Monday 27th October 2014.

Updated documentation.

Users are advised to take sometime to read the updated documentation. For an overview of how to use the API please refer to the API documentation. Please note the API is still beta and there many be large changes that break backwards compatibility based on the user feedback received.