Version 5.3.2 Release Notes

Release Date: May, 2007

PureMessage 5.3.2 consists of the following improvements and bug fixes.

Improvements (5.3.2)

A policy test, "Number of recipients," has been added that is used to perform chosen actions if the total number of recipients for a message is less than, greater than or equal to the number specified.
It is now possible to have a custom logo displayed in the End User Web Interface (EUWI). See "Adding a Custom Logo" in the PureMessage for Unix section of the Sophos Knowledge Base for instructions.
By default, support requests submitted through the PureMessage Manager include attachments with configuration and log data. Previously, only the first 200 lines of each of the various log files were attached. Now, up to 5,000 lines of each log file are included in a compressed format. This provides Sophos support with additional information when analyzing requests. You can see what data will be attached by clicking view next to each selected Attach item on the Send Support Request page.
The pmx-qexpire command-line program now allows you to specify a quarantine reason for expiring a message See the pmx-qexpire man page for more information.
In previous versions of PureMessage, some manual steps were required to switch from Postfix to sendmail or vice versa. This can now all be done via options in the PureMessage installer.

Bug Fixes (5.3.2)

The following problems have been corrected:

Due to a problem with the pmx-reports-set-time-ranges command, one hour of reports data was lost when shifting from daylight savings time (DST) to standard time. (DEF08597)
PureMessage attempts to optimize performance of the PostgreSQL database during installation and upgrades. Those who have already made manual adjustments for PostgreSQL, and want to retain their custom settings, can restore a backup of the postgresql.conf file, which is automatically generated upon install or upgrade. (DEF10514, DEF10326)
Adjustments have been made to pmx-database-vacuum, the PureMessage scheduled job that performs routine maintenance of the PostgreSQL database. This program now removes outdated data more frequently and is able to properly deal with truncated tables as well as data for reports that is split across multiple databases. (DEF10446, DEF09584, DEF10272)
If the pmx-qmeta-index scheduled job was interrupted or stopped before indexing was complete, the job would start from the beginning of the message file. This sometimes resulted in lengthy waits if there was a large number of messages to index. The program is now able to resume approximately where it stopped. (35574)
The certificate-generating functionality of PureMessage has been fixed, and it is now possible to create a self-signed certificate as described in "SSL Configuration" in the Local Services section of the Manager Reference. (DEF10294)
End-users who subscribed to quarantine digests and used the Thunderbird mail client received digest notifications but were unable to release messages from the quarantine. (DEF09888)
Various changes to pmx-reports-consume-message-log (the program PureMessage uses to extract report data from the log files) have increased its efficiency and stability. (DEF10949, DEF10220)
The Policy Mark Hits report was including default policy marks from the message log that did not relate directly to instances where policy mark actions had been triggered. Now, only marks specified using the "Write test data to message log" action are included in the report. (DEF09735)
During anti-spam updates, an error message similar to the following sometimes appeared in pmx_log:
```
      pmx-patch:2: clone: can't write /var/spool/archive/pmx/bin/pmx-spam-compile:
      Permission denied at /opt/pmx/bin/pmx-patch line 78.
```
This error was the result of a mismatched directory path and no longer occurs. (DEF08901)
Depending on how the End User Web Interface was configured, when email users with alias addresses released quarantined messages, the messages would be released to whichever address they had used to log in. Now, all messages are released to the "real" (Envelope to) address, regardless of any aliased addresses. (DEF09402)
Previous versions of PureMessage enabled the insert_rule_hits option in db.conf by default, which sometimes resulted in the associated table to consuming excessive database space. The insert_rule_hits option is now disabled by default in fresh installations of PureMessage. (DEF08032)