Latest Releases

IMF Tune build 7.1.310.07 fixes a problem impacting the DNSxL functionality.

As from next November, Microsoft will no longer release new SmartScreen updates. WinDeveloper has been preparing for this eventuality for some time now. Here is how we expect this change will impact IMF Tune users.

Outlook SafeSenders, BlockedSenders lists often catch administrators unprepared. Users have the power to directly configure how spam is filtered at the server. Luckily Exchange provides for managing these settings from the shell.

Keyword Reporting includes the information that tie email processing results to the IMF Tune configuration. We go through each bit of information and see how everything comes together to make this report an invaluable troubleshooting tool.

Keyword Reporting is the tool of choice when verifying how effective the current IMF Tune configuration is. It allows us to spot weak whitelists and other misconfigurations that might be degrading filtering results.

IMF Tune now also supports Exchange 2016. IMF Tune handles Exchange 2016 as if it were Exchange 2013 without any significant issues.

AWL is most effective when working on emails that regular users send. With their interaction, users are indirectly vouching for their contacts to be trustworthy. On the other hand, emails sent automatically by applications should not be trusted in the same manner.

Exchange 2013 Managed Availability probes the Exchange health status using auto-generated emails. Some of these may end up caught at the IMF Tune Moderator. With many such emails littering the moderation interface, this may become a nuisance.

IMF Tune v7.1 build 7.1.204.20 includes an important fix to the DNSxL functionality.

When moving IMF Tune to a new server or when deploying a second IMF Tune installation, we are often asked: How do I copy the AWL database to the new installation?