Version 5.3.3 Release Notes

Improvements (5.3.3)

• As added security, PureMessage now prompts for the current administrator password when you are changing the password. (DEF11787)
• By default, PureMessage now logs errors to the scheduler_log (located in /opt/pmx/var/log/) whenever a scheduled job fails. Or, the setting can be changed so that both successes and failures are logged. You can also configure PureMessage to automatically deliver a failure notification to the administrator's email account. These options are set in /opt/pmx/etc/scheduler.conf. In addition, support requests sent via the PureMessage Manager now include scheduler_log data by default. (SUG11428)
• A new option has been added to the postgresql.conf configuration file (/opt/pmx/postgres/var/data/postgresql.conf) that includes a timestamp in each pg_log entry by default. (SUG11222)
• Output from the pmx version command now indicates which patch version of PureMessage is installed. This helps Sophos support determine which upgrades and fixes your version includes, should you experience a technical problem. (SUG11251)
• Previously, if users who received regular quarantined digests had temporarily configured their email accounts to automatically respond to all mail (for example, an out-of-office reply), PureMessage would issue an error notification email each time the user's account responded to a quarantine digest. PureMessage is now able to detect if the response is automatic and ignores it. (SUG10882)
• When installing PureMessage 5.3.3 or upgrading to 5.3.3 from 5.3.x, a "superuser" account for the Groups Web Interface is now automatically created. By default, an administrator can log into this account using the PureMessage Manager password that is set during installation. The superuser account has full access to all configured groups and their associated preferences, as well as Groups Web Interface functionality that is not specific to groups, such as reporting and quarantine management. You can use these features as an alternative to the reports and quarantine features of the PureMessage Manager. See the "Quarantine Management" and "Reports" sections of the Administrator's Reference for more information. Users of PureMessage 5.2.x and earlier must create a superuser account manually by following the "Creating a Full-Access Administrator Account" procedure in the PureMessage Groups section of the Administrator's Reference. (SUG10274)

Resolved Issues (5.3.3)

The following problems have been corrected:

• If an administrator performed a search of the quarantine via the Groups Web Interface using Internet Explorer 7, only a single search result was returned, regardless of the number of actual matches. A complete list of search results is now returned. (DEF10383).
• When searching the quarantine via the Groups Web Interface, the date range was not preserved if you attempted to advance beyond the first page in any query result containing multiple pages. (DEF11192)
• When creating a custom policy setting for the Groups Web Interface, specifying any lowercase characters for the --id option resulted in an error message stating that the permission was invalid. Lowercase and mixed case entries are now accepted. (DEF09180)
• Upgrading from PureMessage 5.3.1 to 5.3.2 caused Postfix's header_checks file to be overwritten. As a result, any custom settings were lost. Postfix custom settings are now preserved during upgrades. (DEF11448)
• Due to a database limitation, large numbers contained in the OS Health report sometimes resulted in an "integer out of range" error message. (DEF11285).
• If PureMessage was configured such that the reporting and quarantine/resources data was stored separately, report queries run from the Groups Web Interface returned no results. (DEF10273)
• If you saved a configuration snapshot that included /opt/pmx/postgres/pg.log, the stored snapshot increased in size over time, consuming excessive disk space. This resulted because the snapshot was hard-linked to the actual pg.log file. (DEF11339)
• Improvements to the way time ranges are stored in the database have increased the accuracy of report data. (DEF11743)