PureMessage for Windows/Exchange: version 2.5.0 and internal TNEF mail delivery problems
Customers who have upgraded to PureMessage for Windows/Exchange version 2.5.0 could experience problems with the delivery of internal TNEF mail if they have customized their spam settings.
This issue does not affect Sophos PureMessage Small Business Edition.
PureMessage for Windows/Exchange version 2.5.0 customers are strongly advised to configure their settings to:
- a 'suspected spam' setting of 50 or more
- a 'spam' setting of 90 or more.
This issue has been fixed in PureMessage for Windows/Exchange, version 2.5.1. Sophos recommends that you upgrade now.
What to do
In the PureMessage for Windows/Exchange console tree
- Click 'Jobs' then 'Mail (SMTP)'.
- Click the 'Spam' tab.
- Set the 'spam' slider to 90.
- Set the 'suspected spam' slider to 50.
- Click 'Apply'
For details, see section 4, 'Blocking spam', in the PureMessage for Windows/Exchange startup guide.
Technical details
There are two related issues within PureMessage for Windows/Exchange version 2.5.0:
- Whitelisting of internal email domains and/or addresses does not work if mails are sent in TNEF format by Microsoft Outlook or Outlook Web Access.
- Internal email (in TNEF format) that is quarantined as spam, is not released from the quarantine to the intended recipients.
These issues will predominately affect customers who have configured a low 'suspected spam' or 'spam' rating, and are using the default action 'Quarantine message' for suspected spam.
The recommended setting for 'suspected spam' is a spam rating of 50, and the recommended setting for 'spam' is a spam rating of 90. This issue should not affect customers with these settings.
Customers that have downloaded PureMessage for Windows/Exchange version 2.5.0 are advised to ensure that their 'suspected spam' setting is 50 or higher.
Sophos is currently working on a new version of PureMessage for Windows/Exchange (version 2.5.1) which will fix these issues. This version is scheduled for release during January 2006.
More information on both of these releases will be published on the Sophos website.
If you need more information or guidance, then please contact technical support.
- Article ID: 14138
- Created: 2 Dec 2005
- Last updated: 12 Jan 2006
