Keep up with the latest updates from WinDeveloper by subscribing to the RSS feed. Supply the URL that follows to your RSS reader/news aggregator: http://www.windeveloper.com/news/rss.xml
Wed, 10 Jul 2019
As from the next update, AWL will no longer be limited to whitelisting! Instead we will be able to choose any SCL change action, including the ability to apply an SCL decrement operation.
Wed, 19 Jun 2019
IMF Tune version 8 raised its minimum ODBC Drivers requirement. These may not be readily installed; in which case we have to download and install them ourselves.
Wed, 01 May 2019
This article discusses various upgrade/migration scenarios you may encounter when deploying IMF Tune v8. In both Upgrades and Migrations our primary goal is to retain the configuration settings of the old IMF Tune installation.
Tue, 30 Apr 2019
We are pleased to announce the immediate availability of IMF Tune v8.0. This anti-spam solution is now 14 years old and still keeping up with the latest Microsoft Exchange developments.
Tue, 02 Apr 2019
IMF Tune v8 will see a significant change in its licensing model. With this release we are switching to an on-premises subscription model.
Wed, 13 Mar 2019
Work on IMF Tune v8 is progressing well and we would like to share more details on the platform requirements this version will be targeting.
Fri, 25 Jan 2019
The upcoming IMF Tune v8 is adding support for Transport Layer Security 1.2. This improves support for the latest Windows Server platforms and MS SQL Server versions that are deprecating the older TLS 1.0 protocol.
Tue, 13 Mar 2018
IMF Tune v6 upgrade discounts end on 26th March
Mon, 20 Nov 2017
A new IMF Tune build is now available for download. All the additions concern the IMF Tune Quarantine/Reporting interface. This functionality was lagging behind in IIS and SQL version support. This build is filling these gaps.
Thu, 02 Nov 2017
We have identified a problem when installing the Exchange 2016 built-in anti-spam agents. This concerns Exchange 2016 Cumulative Update 7 released last September. The problem was not present in earlier Exchange 2016 releases.