Build Information for GFI MailSecurity 9 (Full Version)

All Forums >> [Web & Mail Security] >> GFI MailSecurity



Message


Patrizia -> Build Information for GFI MailSecurity 9 (29.Dec.2005 10:02:39 AM)

Note: This topic contains information regarding the changes within the various builds of the GFI MailSecurity 9. 
The first entry will contain information about the latest build of GFI MailSecurity, while the posts below contain information regarding previous builds of the product.




Latest build of GFI MailSecurity 9:- 20060313




C
hanges within this build include:
  • FIXED: When installing on a cluster, Exchange wasn't being detected and therefore VS API support wasn't being installed.
  • FIXED: On Windows 2000 reboot the Email Exploit Engine might fail to initialize causing all email flow to go to failedmails.
  • FIXED: The attachment checking was identifying certain mp3s as text.
  • FIXED: Email loop condition that can occur between GFI MailEssentials and the GFI MailSecurity quarantine when both products are installed on the same machine.
  • FIXED: In some cases the Exchange user counting was failing.
  • FIXED: A file of size 0 bytes when caught by attachment rule will not be downloaded from the Quarantine Store.
  • FIXED: Various user interface validation fixes.
  • FIXED: The issue where sometimes, when a virus engine fails to update and reload causes emails to go to failedmails.
  • FIXED: If during processing the Scan Engine service is restarted, some emails might end up in the failedmails.
Further information can be found at: http://kbase.gfi.com/showarticle.asp?id=KBID002591




The latest version of GFI MailSecurity can be downloaded from:
http://www.gfi.com/pages/files.htm




Patrizia -> GFI MailSecurity 9 (30.May2006 4:52:44 AM)

What's new in GFI MailSecurity for Exchange/SMTP 9?
  1. Web-based configuration, monitoring and quarantine view. With this web-based configuration the administrator will be able to configure, monitor and manage quarantined items remotely from any PC.
  2. Administrators can create Quarantine Search Folders very similar to the MS Outlook Search Folders. Using the search folders, administrators can manage their quarantined emails better and faster. For example, they can configure a search folder for emails quarantined by Virus Checking and a folder for emails quarantined by Attachment Checking; in this way administrators can prioritize which folders they need to look into first (Attachment Checking in this case) and action immediately.
  3. Ability to make searches within the quarantined emails for emails for/from certain users etc. GFI MailSecurity provides the facility to conduct searches within all emails that it quarantines. Such searches can be performed among inbound or outbound emails to or from a particular user, for instance. Searches can also be carried out based on sender, recipient and also quarantine reason, freeing the administrator from the need to go through all quarantined emails one by one.
  4. Now when an email is quarantined, a full threat report is shown in the Quarantine. This means that if there is an email contains an attachment that has been quarantined by Attachment Checking and the Trojan Engine, the administrator can then see the full threat report identified for this email.
  5. The product has been re-engineered and it can now scan emails much faster on machines that have two or more processors.
  6. The Quarantine system is now much faster than the one in GFI MailSecurity 8.




Patrizia -> GFI MailSecurity 9 build 20050727 (30.May2006 5:03:42 AM)

Changes within build 20050727 include:
  • FIXED: Now when quarantine action emails are sent via email, the sender being set is the administrator as specified in the Settings configuration node
  • FIXED: The Attachment Checking "Block All Files Greater than: X KB" feature was blocking all files greater than X Bytes instead
  • FIXED: Updated the HTML Threat engine internal database to support CSS (style sheets) sanitization
  • FIXED: Previously, when processing a partial cab file the processing thread was hanging
  • FIXED: Fixed a handle leak in the Attendant service
  • FIXED: In certain situations, any changes from configuration where not being read by the engine.




Patrizia -> GFI MailSecurity 9 build 20050811 (30.May2006 5:05:07 AM)

Changes within build 20050811 include:
  • FIXED: Sometimes when installed on the same machine as Exchange server, emails where being queued.
  • FIXED: Incorrect information displayed by the real time monitor.
  • FIXED: Emails to/from particular users would end up in failed mails due to an issue in the AD user lookup.
  • FIXED: On rare occasions the GFI MailSecurity Attendant service was crashing when one tries to stop it.
  • FIXED: Various issues when accessing the web based configuration / quarantine like ‘Access Denied’ and 'Field Input' errors.
  • NEW:  Now you can configure, monitor and access quarantine through a local configuration and not through an IIS WWW page.  More information on how to use this can be found at: http://kbase.gfi.com/showarticle.asp?id=KBID002417




Patrizia -> GFI MailSecurity 9 build 20050826 (30.May2006 5:06:14 AM)

Changes within build 20050826 include:
  • FIXED: When an email contained excessive amount of recipients (500K and above), there was a possibility that IIS service would crash.
  • FIXED: When an email was destined to multiple recipients in different domains, sometimes the email could have ended up in the FailedMails folder.




Patrizia -> GFI MailSecurity 9 build 20051123 (30.May2006 5:07:22 AM)

Changes within build 20051123 include:
  • NEW: Complete new User Interface theme and some major design changes.
  • NEW: Support proxy servers with authentication for the virus updates download process directly from configuration.
  • NEW: Added an option where the administrator can set the virus updates mechanism to only send email notification on unsuccessful updates and not successful ones.
  • NEW: Introduced a new tool (switch board) which enables the user to switch between local and IIS UI mode and set appropriate access control lists in the case of IIS UI mode.
  • NEW: Changed the backend technology for the Email Exploit Engine and removed dependency on the mshtml.dll component. Fixed certain issues which existed due to bugs in mshtml.dll.
  • NEW: Added an email notification template parameter "[SERVERNAME]" which will expand to NetBIOS name of machine where the virus updater service is running.
  • NEW: In the Kaspersky configuration, a radio option was added in which the customer can choose to download the Kaspersky SuperSecure files instead of the default Kaspersky files.
  • FIXED: Various small HTML UI fixes and more input validation.
  • FIXED: Introduced apostrophe escaping in the SMTP User Lookups.
  • FIXED: Found and fixed a handle leak in the patch checking process.
  • FIXED: Fixed issues where the HTML threat engine was causing certain HTML emails to be incorrectly rendered.
  • FIXED: In Attachment Checking, fixed an issue with NDRs and read-receipts always being blocked when the Block All Except option is used.
  • FIXED: Fixed bug in which users with just one proxy address were not retrieved by user lookup.
  • FIXED: Fixed an issue in which CAB files were being blocked for exceeding the number of files allowed, even if they did not really exceed this limit.
  • FIXED: Fixed an issue where the avapicfg.mdb file was growing in size automatically.
  • FIXED: In certain cases the configuration's IIS virtual directory was not being removed during un-installation, which could cause problems during an upgrade.




Patrizia -> GFI MailSecurity 9 build 20060104 (30.May2006 5:19:48 AM)

Changes within build 20060104 include:
  • NEW: Support for VS API. As from this build, when the product is installed on the same machine as Exchange it will install also a VS API interface giving it the ability to scan the Exchange Information Store with the anti-virus engines.
  • FIXED: Large number of Mime Addresses in a quarantined email were NDR 5.6.3 was generated.
  • FIXED: Optimization was made to the user resolution process.
  • FIXED: Various fixes which where causing incorrect removal of HTML tags by HTML Threat Engine.
  • FIXED: Emails redirected by an Outlook rule that were ending up in FailedMails. In case there were no SMTP recipients in the mail to be processed, an exception was raised causing the mail to be moved to the failed mails folder. This happened when a forwarding rule in Exchange is applied on incoming mails, for example.




Page: [1]