IMF Tune v6.1 - Forefront Protection 2010 for Exchange Support
Check the following frequently asked questions to quickly resolve/answer common questions.
IMF Tune is installed on the Exchange server machine. Exchange versions 2003, 2007, 2010 and 2013 are supported. The following is the list of supported platform/Exchange server combinations:
Exchange 2003 SP2 - Windows 2003 (x86), SBS 2003 (x86)
Exchange 2007 - Windows 2003 (x64), Windows 2008/2008 R2 (x64), SBS 2008 (x64)
Exchange 2010 - Windows 2008/2008 R2 (x64), SBS 2011 (x64)
Exchange 2013 - Windows 2008 R2 (x64), Windows 2012 (x64)
In Exchange 2007/2010 IMF Tune must be installed on the Edge or Hub transport server roles. The Exchange Content Filter or Forefront Protection 2010 for Exchange must also be installed.
In Exchange 2013 a distinct Hub Transport server role is no longer available. Instead this is included with the Mailbox Server. Thus IMF Tune must be installed on the Mailbox Server role. The Exchange Content Filter must also be installed.
IMF Tune enables the insertion of SCL ratings into the email subject. This is inserted as a prefix in the format (SCL: x). Thus at the junk email folder one can easily sort all emails by SCL rating. Since false positives are most likely to happen with the lowest SCL rating, sorting enables verification of these emails first. Read Complete Article...
IMF Tune does not change anything in the way emails are moved to the junk email folder. Hence this is purely a matter of configuring the Exchange Content Filter/Intelligent Message Filter and the email clients. Read Complete Article...
For emails to be deposited to the junk email folder rather than the inbox you need to make sure that this functionality is enabled at the client mailbox. But before doing this make sure that the Content Filter/IMF is also correctly configured at the Exchange Server. See more details from: How do I configure emails to be deposited to the junk email folder?
If you already verified the Exchange Server settings, then check that the junk email folder is enabled at the client mailbox. This can be done through Outlook Web Access OWA. Other possible methods for enabling the Junk Email folder are available but depend on your Exchange Version. Read Complete Article...
You need to make sure that the Exchange 2003 IMF, Exchange 2007/2010/2013 Content Filter or Forefront Protection 2010 for Exchange Anti-Spam is enabled for IMF Tune to work. Read Complete Article...
Typically you need to do this when spam still manages to reach the recipient Inbox. Read Complete Article...
Optimizing SCL threshold configuration typically aims to
To get the best out of IMF we need to monitor how a set of configuration settings is performing. IMF Tune helps in this task in the following ways:
At IMF Tune create multiple Archive/Logging Profiles. One for each of the SCL ranges requiring independent logging/archiving. In this manner you can setup a unique log file/archive directory for each of the SCL ranges.
In IMF Tune, filtering is a two stage process. First we have the Exchange IMF/Content Filter/Forefront stage. Following that we have IMF Tune itself. Emails blocked at the first stage are not processed by IMF Tune.
IMF Tune can perform all the gateway blocking actions itself. Hence the correct setup is that to disable Gateway filtering at the Exchange IMF/Content Filter/Forefront and configure any of the Archive/Quarantine, Delete or Reject actions at the IMF Tune configuration.
The Exchange 2007/2010/2013 Content Filter provides the Quarantine, Reject and Delete gateway blocking options. These may be replaced at IMF Tune by the Reroute, Reject and Delete Email Handling actions.
The Forefront Content Filter provides Quarantine, Reject and Delete gateway blocking. The Forefront Quarantine is a central store, accessible from the Forefront Management Console. These are replaced at IMF Tune using the Web Moderator/Reporting component and the Email Handling Reject and Delete actions.
Exchange 2003 IMF provides the Archive, Delete and Reject actions. At IMF Tune the same functionality is provided by configuring Archiving profiles and using the Email Handling Reject and Delete actions. Read Complete Article...
The Exchange 2003 Intelligent Message Filter Gateway Blocking includes an Archiving Action. This is effectively a Delete and Archive operation since archived emails are not delivered.
IMF Tune does not list Archiving in its Action list but rather makes archiving always available independently of which action is performed. Thus archiving is possible whether you Accept, Reroute, Delete or Reject emails. For more details refer to: Which IMF Tune actions replace the Exchange IMF/Content Filter/Forefront Gateway Blocking?
Through the detailed logging information generated by IMF Tune it is possible to identify some common spam sources. For example the originating host IP can be useful in setting up IP blacklists.
This information could also be processed through one of the many reporting tools available on the market. All of these typically support the CSV format generated by IMF Tune. Hence you should be able to import the data directly and then generate reports based on the capabilities of the tool used.
In this case it is best to generate separate log files for the higher range of SCL values where the likeliness of false positives is minimal.
No. Emails rejected through Exchange filtering never reach IMF Tune.
IMF Tune will handle these as whitelisted. It will apply any email handling settings as configured for whitelisted emails.
IMF Tune couples tightly with the Exchange Content Filter/IMF. Hence which emails are processed or left unprocessed is determined by Exchange and not IMF Tune.
By default the Content Filter/IMF won't process emails from an authenticated connection. Thus these are handled as unprocessed by IMF Tune.
Another scenario giving rise to unprocessed emails is when the Content Filter/IMF is not enabled.
999 is the SCL value assigned by IMF Tune to blacklisted emails. At the moment the Exchange Content Filter/IMF does not define an SCL for blacklisting. Thus we had to invent one. We chose a value that is much larger than the largest defined SCL. For this reason, whenever choosing to expose the SCL value, 999 will be set in case of blacklisted emails.
With Whitelisting, Blacklisting and SCL Rules it is possible for a single email to give rise to multiple matches. IMF Tune follows a "play safe" rule, and the lowest SCL rating is applied. For example if an email contains both a blacklisted keyword and a whitelisted keyword, the email is whitelisted.
Extending this concept further, if an email matches an SCL Rule configured to set the SCL to 5 and also matches a blacklisted keyword, than the final SCL will be 5.
SCL Rules applying 'increment by 'and 'decrement by' operations are considered to have the lowest priority. The increments and decrements are only computed if no other match is found that would set the email to a fixed SCL value. If computed, increments and decrements add up so that the final SCL value is the net result.
So to recap, the final SCL rating is assigned based on these priority rules:
This issue is mostly of concern when running Exchange 2003.
In Exchange 2007/2010/2013, we configure the perimeter IP address list from the shell with
In Exchange 2003 we can also configure the perimeter IPs at the System Manager. However IMF Tune does not support these settings. So in Exchange 2003, IMF Tune always ends up seeing the last IP. In our example this would be the internal relay server IP.
In this case you may want to consider setting up an SCL Rule for the RFC2822 Received header. For example consider the IP 127.0.0.2. Let's say you want all emails originating from this IP to be deposited to the Junk Email folder or to be blacklisted.
In this case you can setup a mapping specifying that if the Received header contains 127.0.0.2 the SCL is set to 5. Here 5 is an SCL value for which emails are configured to be deposited to the Junk Email folder.
For more details on how to setup IMF Tune refer to the FAQ How do I force an email to go to the Junk Email Folder?
For more details on the RFC2822 Received header refer to: http://www.faqs.org/rfcs/rfc2822.html
These settings apply to functionality provided either by Exchange itself or by the Intelligent Message Filter. This is done to provide a centralized view of all settings relevant to anti-spam protection and to increase the awareness of the Exchange 2003 out-of-the-box anti-spam functionality. Thus any modifications should be done through the standard Exchange management console.
The IMF Tune web interface requires a Microsoft SQL backend database. All MS SQL versions from 2000, 2005, 2008 and 2012 are supported, including the free MS SQL Express editions.
For the system to work IMF Tune requires an SQL Server that supports both Windows Authentication and SQL Authentication. This is sometimes referred to as mixed mode authentication. In case SQL Authentication is not enabled, IMF Tune will be unable to upload any emails to the database server. Complete Article...
The IMF Tune Moderator/Reporting Web Component displays date and time information in various parts of the interface. Different countries have differing methods for formatting such information. For example in US the short date format used is M/d/yyyy. In the UK the format dd/MM/yyyy is used instead.
The Web Component fixes the format to be used for displaying time information at installation time. This format may not be the one in use in your region. In that case, follow the procedure presented here to change it. Complete Article...
Email to: email@example.com
IMF Tune on first install runs in free 30day evaluation mode. Once evaluation is over it stops processing emails. At this point a license key must be supplied in order to restore full product functionality.
You may obtain an extended evaluation period by contacting:
When licensing IMF Tune the following information is required:
IMF Tune provides a number of license options based on the number of mailboxes being serviced. Currently license levels for 15, 30, 50, 100, 200, 500 and unlimited mailboxes are available. You need to choose a license that matches or exceeds the number of mailboxes serviced by your organization.
Once the license type is identified, order one license for each machine where IMF Tune is to be installed. For example an organization servicing 150 mailboxes running IMF Tune on two servers would require 2 licenses for 200 mailboxes.
Note that in general IMF Tune is only installed on the internet facing servers and not backend mailbox servers. However this depends on your network configuration.
For help on choosing the correct license contact: firstname.lastname@example.org
No. The feature set is identical.
A license is only needed for the servers where IMF Tune is installed. Typically anti-spam protection is installed on the internet facing bridgeheads. Thus these would be the only servers requiring IMF Tune.
The secure ordering system uses SSL to encrypt your details so as to safeguard sensitive data such as the credit card number.
No. You just purchase the license and use it with no other payment obligations. You may choose to subscribe to a yearly maintenance agreement. However this is optional.
Contact email@example.com they will be able to supply you with an evaluation license.
No. The IMF Tune evaluation product is effectively the full product. All you need is to supply it with a license key and no reinstallation is required. For details on how to license the product refer to the User Manual.
For a yearly fee you can extend product support. Extended support always starts from the date when the previous support contract expires. Support can only be renewed within 60 days of the previous support contract expiry. To extend support contact firstname.lastname@example.org.
Support should be renewed within 60 days from the expiry of the last support contract. If you purchased IMF Tune on 1st June 2006, support will expire on 1st June 2007. Following that you have up to 30th July 2007 to renew support.
Email to: email@example.com