Version 6.0 Release Notes

Improvements (6.0)

IPv6 Support

PureMessage now supports IPv6, allowing you to send and receive mail from IPv6 addresses as well as IPv4 addresses. In addition, PureMessage's search and reporting features now recognize IPV6 entries.

Whether you are installing PureMessage or upgrading from version 5.6.1, the installer will ask if you want the server to recognize both IPv4 and IPv6 addresses or just IPv4 addresses.

Updating from version 5.6.1 to version 6 is not a typical upgrade. You will install PureMessage 6 alongside your existing 5.6.1 installation. Optionally, you can then migrate policy settings and other data from PureMessage 5.6.1 to PureMessage 6 by using the PureMessage migration script. For more information, see Upgrading PureMessage for UNIX to Version 6.

Operating Systems

• Support has been added for the following operating systems:
  • Red Hat Enterprise Linux 6 (64-bit)
  • CentOS 5.6 (32-bit and 64-bit)
  • Debian 6 (64-bit)
• Support has been discontinued for the following operating systems:
  • Red Hat Enterprise Linux 4 (32-bit and 64-bit)
  • All previously supported versions of FreeBSD
  • Solaris x86
  • Solaris 9
  • SuSE Enterprise Server 10
• On Linux, glibc 2.5 or later is now required.
• PureMessage continues to support Solaris 10, but only on update 6 and later, running on SPARC architecture.
• PureMessage supports Oracle Communications Messaging Exchange Server (formerly JSMS), but no longer supports use of the JSMS plug-in, pmxchannel.conf. You must now use Oracle's built-in milter support.

Performance Improvements

Updates to core components, including Postfix, PostgreSQL and Apache, provide added security, resolve outstanding issues, and improve performance. Optimizations to the End User Web Interface improve responsiveness by an estimated 20%.

Log Search/Forensics Improvements

A revamped forensics system provides new features, added resiliency, and improved reliability. Search reliability and accuracy has been improved, and you can now search logs by subject. Indexing is more robust, particularly when dealing with unparsable log entries or files. (#60219)

Refreshed User Interface

All user interfaces, including the PureMessage Manager, Groups Web Interface, and the End User Web Interface have all been updated with a modern, clean new look.

Other Changes

• PureMessage now provides full support for Delivery Status Notifications.
• The feature that was used to create snapshots of currently installed PureMessage components and their configuration has been removed.
• It is now possible to use an SSL connection with the PostgreSQL database.
• A configuration file, event-notify.conf, has been added so that different notification thresholds can be specified for some scheduled jobs. For more information, see the scheduler.conf man page.

Resolved Issues (6.0)

• Improved error handling of DKIM timeouts. (#74783)
• Resolved an issue where, when running the mail command (part of the mailx package), the message could be incorrectly interpreted as an inbound message instead of an outbound message. (#10499)
• Removed the ability to edit the "Maximum Bytes to Scan" setting. This value should not be changed and could introduce abort-retry issues for large files. (#65692)
• Resolved an issue where the time in search results was not properly converted to UTC, and did not match the preview window. (#24326)
• Changed the behavior of searching the logs so that long lists of results return the newest 1000 results instead of the oldest 1000 results. (#24389)
• Resolved an issue where searching the logs would not find certain addresses with numeric local-parts. (#24303)
• Addressed many other stability issues.