SpamFilter 4.7.1.141 is officially released |
Post Reply |
Author | |
LogSat
Admin Group Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
Posted: 28 June 2015 at 9:48am |
We have officially released the new SpamFilter ISP and SpamFilter Enterprise v4.7.1.141. This release is available for download in the registered user area of our website. A free Evaluation copy is also available for all other users. As always, this upgrade is free for all users with a current software maintenance. The changes since the latest official release (v4.7.0.136) are as follows: // New to VersionNumber = '4.7.1.141'; {TODO -cNew : Improved support for the XFORWARD extension by not advertising XFORWARD in EHLO response unless IP is listed in AuthIPsForXforwardCommand} // New to VersionNumber = '4.7.1.139'; {TODO -cNew : Added support for the XFORWARD extension - this allows the placement of a server/appliance that processes inbound emails *before* they reach SpamFilter, and thru the use of XFORWARD the appliance/server can provide SpamFilter with the original IP address of the sender, allowing SpamFilter to perform all the IP-based tests on that original IP} {TODO -cNew : Added the parameter AuthIPsForXforwardCommand=aaa.bbb.ccc.ddd in the SpamFilter.ini file to restrict the use of XFORWARD only to the IPs listed in AuthIPsForXforwardCommand} {TODO -cFix : Bug introduced starting from 4.6.1.119 - After outputting the 667 SMTP error code when rejecting an email due to one of the content filters, SpamFilter was also outputting the extra line "554 4.2.0 Transaction failed"} {TODO -cNew : To reduce lingering connections SpamFilter is now forcing the disconnect of the remote server when an email is rejected to one of the content-based filters} {TODO -cNew : Added the logging of the "From" header also indicating whether it matches or mismatches the email specified in the MAIL FROM command} {TODO -cNew : Added the parameter ProcessListEvenIfAutoWhiteListForceDeliveryDisabled==0 in the SpamFilter.ini to allow SpamFilter to still allow SpamFilter to process the entries in the WL_AutoWhiteListForceDelivery even if AutoWhiteListForceDeliveryEnabled=0} Edited by LogSat - 13 August 2015 at 9:43pm |
|
Post Reply | |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
This page was generated in 0.180 seconds.