Version 5.5.4 Release Notes

Release Date: April, 2009

Improvements (5.5.4)

Reports that are run and viewed through the Groups Web Interface can now be run as scheduled jobs, with the results delivered by email to the chosen recipient. For more information, see the pmx-reports-mailer-v2 man page, and Managing Scheduled Jobs in the Manager Reference. (SUG18525)
This release includes version 2.7.1 of the Sophos Anti-Spam Engine, which has improvements that ensure continued best protection against spam threats.
A new message_exception_action can now be configured in /opt/pmx/etc/pmx.conf. Prior to this release, when the PureMessage policy engine encountered a message that resulted in a message exception error, the message was always quarantined. Now, you can add an entry to pmx.conf to reject, discard, or keep exceptions (the default is quarantine). So, for example, to reject all message exceptions, add the following line to pmx.conf:
```
message_exception_action=reject
```
(SUG12433)

Previously, installations failed for those who attempted to upgrade to PureMessage 5.5.x if they had created a symlink to the /opt/pmx/postgres directory. Now, if you attempt to upgrade with a symlinked postgres directory, the PureMessage installer will warn that the upgrade cannot be completed until the directory is re-established in its expected location beneath /opt/pmx/. (DEF29840)
It was possible, when using the %%HITS%% variable, to exceed the 998 character limit for messages that is specified in RFC 5322. In some cases, this caused messages to be rejected by mail servers that are enforcing this standard. The lines will now wrap, assuring RFC compliance. (DEF35415)
In previous versions of PureMessage, it was possible to delete policy lists, including end user lists, that were currently in use by the policy engine. A safeguard introduced in this release has corrected this. (DEF35606)
The introduction of PureMessage 5.5 included fixes that caused the blocklist_log in /opt/pmx/etc/logrotate.d/ to be unavailable. You must upgrade to 5.5.4 to restore this feature. (DEF33626)