Release Date: July 27, 2005
PureMessage 5.0.3 consists of fixes for various bugs,
including:
- PureMessage now uses an updated version of PostgreSQL
(7.4.8), eliminating some reported security vulnerabilities.
- In multi-server deployments using a single database server, running
pmx-reports-set-time-ranges on multiple servers at the same time returned
errors. This has been fixed.
- Messages for mapped recipients were not approved and remained in the quarantine. Messages are
now approved and displayed in the quarantine queue.
- PureMessage's report data collector can now handle
sender and recipient names longer than 256 characters.
- Previously, a failed quarantine request was not cleared from the database, and it remained
there until an SQL statement was issued to remove it. This has been fixed.
- Bar graphs for reports would not display properly if the report covered a period longer than
12 hours. This has been fixed.
- When used with the PostgreSQL database, PureMessage
did not correctly display results of the "group by" parameter on the quarantine query results
page, which displayed an "x1" beside each message, regardless of the number of messages that
matched the search criteria. This has been corrected so that the appropriate number (for
example, "x2", "x3") displays next to the aggregated result.
- Running pmx-qmeta-index and pmx-digest on messages
with Japanese characters in the subject line consumed 100% of a machine's CPU, and the digest
processing resulted in segmentation errors.