IMF Tune v7.1 - Bringing Back the Exchange Connection Filter
September 06, 2006
We just released IMF Tune build 2.8.209.01 and is now available for download. This includes an important fix and some enhanced functionality. Because of the fix, all IMF Tune v2.8 users should upgrade.
FIX - A problem within IMF Tune could cause a failure within the inetinfo.exe process leading it to restart
This problem can be triggered when processing HTML email bodies containing a specific encoding sequence. The email leading to this problem is rejected notifying its sender that delivery failed.
As a consequence the inetinfo.exe process terminates and restarts automatically. During the time taken for the restart, email delivery is suspended. The failure will also generate application event log errors of this type:
Event Type: Error
Event Type: Error
The IMF Tune SCL Management allows for configuring matching rules against any email header. These rules are applied against each of the headers individually.
In an email you typically have multiple Received headers, one for each host through which the email is routed for delivery. As an example let's assume an email contains the following Received header sequence:
In earlier IMF Tune builds, an SCL Management rule for the Received header would be applied twice, once for each of the headers. Each time the matching outcome is determined possibly leading to multiple matches. In the latest IMF Tune build, all the Received headers are processed together and a single matching operation is performed.
To appreciate the difference, consider an SCL mapping rule of the type:
If Received header contains Host1 AND Host2 set SCL to whitelisted
In previous IMF Tune builds this condition (Host1 AND Host2) would not lead to any matches since none of the headers contain both host names. However in the latest build the condition would match since both headers are joined and processed together.
To check if you already have the latest IMF Tune v2.8 build, open the configuration and select the WinDeveloper category. If the build number shown matches 2.8.209.01 then there is no need to upgrade.