Release Date: April, 2009
Resolved Issues (5.5.4)
- Previously, installations failed for those who attempted to upgrade to PureMessage 5.5.x if they had created a symlink to the
/opt/pmx/postgres directory. Now, if you attempt to upgrade with a
symlinked postgres directory, the PureMessage installer will warn that the upgrade cannot be
completed until the directory is re-established in its expected location beneath
/opt/pmx/. (DEF29840)
- It was possible, when using the %%HITS%% variable, to exceed the 998 character limit for
messages that is specified in RFC 5322. In some cases, this caused messages to be rejected by
mail servers that are enforcing this standard. The lines will now wrap, assuring RFC
compliance. (DEF35415)
- In previous versions of PureMessage, it was possible
to delete policy lists, including end user lists, that were currently in use by the policy
engine. A safeguard introduced in this release has corrected this. (DEF35606)
- The introduction of PureMessage 5.5 included fixes
that caused the blocklist_log in
/opt/pmx/etc/logrotate.d/ to be unavailable. You must upgrade to 5.5.4 to
restore this feature. (DEF33626)