Version 5.2.1 Release Notes

Improvements (5.2.1)

EUWI Performance Improvements

This version of PureMessage includes changes that improve the response time of the End User Web Interface (EUWI). Management tasks peformed via the EUWI are completed approximately six times faster than they were in PureMessage 5.2.

If you have been running PureMessage with the EUWI option, it is recommended that you edit the enduser_ui.conf file to take advantage of the performance enhancements. For instructions, see the 'Upgrade Guide' section in the PureMessage Getting Started guide.

If you are installing PureMessage 5.2.1 as a fresh installation, the improvements will take effect automatically.

Japanese Character Support

A variety of enhancements have been made to allow PureMessage administrators who are based in Japan to configure policy support for Japanese characters.

<encoding options>
    iconv_enabled = yes
</encoding>

With this option enabled, PureMessage can access libiconv, the library used to convert from one character encoding to another.

Support for Japanese characters has been added in the following areas:

• A new option has been added to the utf8.conf configuration file that allows PureMessage to access libiconv, a library used to convert from one character encoding to another. This option gives PureMessage the ability to recognize Shift-JIS and EUC-JP encodings. Edit utf8.conf so that the iconv_enabled option is set as follows:
• The policy.siv file, which was previously restricted to characters in the Latin1 range, can now now handle Japanese characters as well.
• When using the 'verbatim' setting in the PureMessage Manager's policy editor or when editing policy.siv directly, specified strings can now contain Japanese characters for the following policy actions: Replace message part (pmx_replace_body), Add banner (pmx_add_banner), Notify (pmx_notify).
• Japanese characters can be used to specify a 'Reason' for actions in the PureMessage policy edtior or the policy.siv script.
• You can use Japanese characters when specifying text for the Attachment name (pmx_attachment_name) and Subject (header) policy tests in the PureMessage Manager's policy editor or the policy.siv script.
• The suspicious attachments policy test can detect filenames containing Japanese characters.
• All PureMessage lists are now stored as UTF-8 instead of Latin1. However, manual editing of lists or the lists.conf file must be done in UTF-8 to ensure that the files continue to work as expected.
• Address maps (Notifications address map and Recipient aliases map) now accept Japanese characters.
• A new option has been added to the Message Source tab. When viewing details for an individual message in a list of quarantine query results, you can click original on the Message Source tab to view the raw source of a message in a new browser window. This option is useful in cases where email messages are not displayed correctly in the PureMessage Manager because they are either incorrectly formatted or use an encoding that is not yet supported by PureMessage. After clicking original to open the source text in a new browser window, you can change the encoding setting of the browser as a test to help determine if a message is spam or legitimate mail.
• Messsages with Shift-JIS and EUC-JP encodings are now displayed properly in the PureMessage Manager and the End User Web Interface (EUWI) if the character set encoding is specified correctly in the message.

PureMessage Monitor

This version of PureMessage includes the PureMessage Monitor, a utility that monitors the message_log for specified items, sets thresholds per item and triggers one of four possible responses when the thresholds are exceeded. The possible responses are notification by email, creation of an entry in a specified log file, addition of an entry to a specified PureMessage list (such as addition of an IP address to the blocked senders list), or the temporary addition of an entry to a specified PureMessage list (the entry is removed after a specified period of time).

Bug Fixes (5.2.1)

• Due to some problems with pg_autovacuum, this PostgreSQL utility has been replaced with pmx-database-vacuum, which addresses the problem of the former utility's occasional failure. The pmx-database-vacuum application now appears as a default sceduled job in the PureMessage Manager's Scheduled Jobs table. (#46002)
• A problem with digest_state entries not being properly expired has been fixed, leaving only valid digest_state entries. (#40035)
• Several small problems with publications have been fixed. Custom lists were always reported as being out of sync in the PureMessage Manager's Server Groups: Policy publication page. Publications had not been able to sync zero-length files. Publications were not indicating which files were out of sync. (#40790, #46620, #46622)
• A problem in which messages quarantined for custom reasons in the policy were not included in the digests has now been fixed. (#46830)
• Two changes have added new information to the PureMessage message_log. The message_log now records the IP address of the first untrusted relay ("fur") encountered in the received headers. If all relays are trusted, the value is set to "none". Also, the message_log now records when a message has been scanned for viruses in the "vs" entry. (#46819, #47184)
• When retrieving an email address from LDAP to create a list, you can now use %u to retrieve the user portion and %d to retrieve the domain portion. These are in addition to the only former option, which allows you to retrieve the entire address using %s. (#47109)
• If the policy.siv script was configured to include attachment information in report data, the scheduled job Reports: Consume Message Log (pmx-reports-consume-message-log) would fail if it encountered message_log entries containing "at" keys with more than 64 characters. This has been fixed. (#47517)