Version 5.5.8 Release Notes

Improvements (5.5.8)

• The version of PureMessage's PostgreSQL database has been updated to 8.3.7 to protect against potential vulnerabilities. (DEF35495).
• For improved security, PureMessage now requires SSLv3, TLSv1, or another protocol newer than SSLv2 (which is no longer supported). (DEF37082)
• A new feature, available on the Server Groups tab of the PureMessage Manager, indicates which servers are running the End User Web Interface/ Groups Web Interface service. The HTTP (RPC/UI) column on the status page shows whether the service is "running" or "stopped." Since log searches are not supported on servers using the sendmail mail transfer agent, you should disable the HTTP (RPC/UI) service on these servers. (SUG38431)

Resolved Issues (5.5.8)

• In some cases, policy rules that used pmx_mark or pmx_mark1 were not logged accurately. This has been fixed. (DEF43104).
• The pmx-logsearch-index scheduled job would sometimes hang, slowing performance of the PureMessage server. In such cases, it was necessary to kill the log search process in order to resume normal operation. This has been fixed. (DEF41356)
• The log search timeout configured in /opt/pmx/etc/logsearch.conf now takes precedence over the default connection timeout. Log searches will time out in accordance to whatever is specified in remote_search_timeout. (DEF42268, DEF47116)
• In some cases, PureMessage was unable to detect attachments when the "Attachment name" (pmx_attachment_name) test was used on messages containing certain Japanese characters. (DEF41801)
• Sometimes, using the “Forward to” action (pmx_forward) action, had the unintended consequence of indexing messages that were queued for delivery, resulting in processing delays and excessive consumption of disk space. This has been fixed. (DEF42233)
• Unrecognizable characters in Shift JIS-encoded messages were resulting in numerous verbose error messages. This has been fixed. (DEF40855)
• The end user license agreement (EULA) for PureMessage has been updated. (WKI41149)
• Due to an inefficiency in database handling, the accuracy of quarantine-based reports was compromised. This has been fixed. (DEF30098)
• The structure of the /opt/pmx/var/digest/pending directory has been modified to include subdirectories. This provides more efficient maintenance of quarantine digest messages. (SUG09183)