Release Date: October 24th, 2005
PureMessage 5.1 consists of the following new features
and bug fixes.
New Features (5.1)
- MTA Level IP Blocking
- MTA level IP blocking rejects messages originating from IP addresses blacklisted by
SophosLabs. Enabling this option can improve
performance by blocking spam before it reaches more complex tests in the Policy such as the
Sender Reputation (DNSBL) Anti-Spam tests.
- Policy Level IP Blocking
- The pmx_blocklist test is a policy-level implementation of IP blocking
which uses the same data as MTA level IP blocking. It allows more flexibility in handling
messages from blocked IP addresses and can provide more information about those messages in
the logs. By using the IP addresses in the 'Received' headers, rather than just the connecting
IP address, pmx_blocklist is effective even if the PureMessage server is one or more hops behind the network
gateway.
- Improved Internationalization
- This release provides further enhancements related to internationalization, including
improved handling of multi-byte characters.
- Reports
- In addition to multiple Reports bug fixes, this release includes an updated report on
policy-level IP blocklist activity
- Increased anti-spam updates
- PureMessage 5.1 includes an increase in the
frequency of anti-spam data updates to every 5 minutes
Bug Fixes (5.1)
- Resolved an issue where creating policy rules based on LDAP lists and maps in which multiple
LDAP servers were specified sometimes caused the milter to hang. (#40193)
- Fixed a bug where the Scheduler service could progressively consume more resources over
time. (#39923)
- Resolved an issue where upgrading PureMessage would
not preserve Postfix configuration files. (#40212)
- Fixed a bug where pmx-reports-consume-message-log sometimes took a long
time to run and consumed excess CPU resources. (#40495)
- Fixed a bug where pmx-reports-consume-message-log was unable to proceed
with some period id values. (#41291)
- Resolved an issue where the bar chart for the Quarantine Size report did not display
correctly. (#40014)
- Resolved an issue where some reports would only show 72 hours worth of data. (#40471)
- Fixed a bug where pmx-reports-consume-message-log failed if the
message_log contained bad data. (#40752)
- Fixed a bug where a single dot was not escaped when sending filter results back to Postfix.
(#39636)
- Fixed a bug where pmx-reports-consume-message-log would process log
files beyond the specified (or default) max lines count. (#40951)