GFI is pleased to announce the availability of GFI MailSecurity 10.1 for Exchange/SMTP Service, BETA 1 (build 20091103). This BETA release gives our customers the opportunity to perform acceptance or in-house testing of GFI MailSecurity 10.1 before the final production release. As this build is currently a BETA, we discourage installations on mission-critical, live server environments. Changesin this BETA release: NEW: Introduced support for Microsoft Exchange 2010. NEW: Introduced support for Microsoft Windows 2008 R2. NEW: Introduced support for the new AVG v1.7.x scanning engine, along with performance improvements in the integration of the AVG engine. NEW: The product's setup screens and user interfaces have been updated to include the new GFI corporate identity. FIXED

The following patches have been released for GFI MailSecurity (build 20090819) Notes: Unless otherwise specified, all patches listed in this article will be included in newer builds of GFI MailSecurity. Installation instructions are included with the download. Patch: MSEC10PATCH2009100601

Description: Under certain conditions, emails with large attachments cannot be released from the Quarantine Store, and the error Item part cannot be found is returned. Download Link: MSEC10PATCH2009100601.zip

When installing GFI MailSecurity on a Microsoft Exchange 2007 server one of the following combinations of Microsoft Exchange 2007 Server Roles must be present: Mailbox and Hub Transport Hub Transport Edge Transport In a Microsoft Exchange 2007 clustered environment, only the Mailbox Role can be installed on the machines which are part of the cluster. The other roles will need to be installed on separate machines. Because of this, GFI MailSecurity needs to be installed as part of the Microsoft Exchange 2007 installation which is not clustered. GFI MailSecurity would need to be installed on the a server running either the Hub Transport or the Edge Transport Role as discussed above. Alternatively, you can also install GFI MailSecurity on a separate machine in gateway mode. Notes: When GFI MailSecurity is installed in a Microsoft Exchange Ser

The following procedure explains how to re-create the GFI MailSecurity Quarantine database should the GFI MailSecurity Quarantine database become corrupt. Note 1: This procedure will delete all email found within the GFI MailSecurity Quarantine.

Note 2: This procedure applies to GFI MailSecurity Build 20090526 and later. Stop GFI MailSecurity Attendant service Delete all folders found in the following directory:

<GFIContentSecurityMailSecurityQuarStoreFB>

Note: Only the contents of the QuarStoreFB need to be deleted. The QuarStoreFB folder should not be deleted.

Open command prompt and change the directory to <GFIContentSecurityMailSecurityMiddleLayer> Run the following command:

qssfbcreate.exe /defaultpath /debuglog c:fdb.log

The quarantine databases will be

GFI MailSecurity 10 Service Release 10 (build 20090819) has been released and is available for download.

Changes within this build include: FIXED: Emails destined to the Quarantine are not saved to the Quarantine if the content-type header is larger than 50 characters. FIXED: On a Turkish Windows OS, the Quarantine operations were failing due to different localised characters used in the data retrieval queries. FIXED: Emails with large headers or filenames can cause errors in the Quarantine. FIXED: When a quarantined email having multiple recipients is approved, it is not delivered to the last recipient in the list. FIXED: In the Quarantine User Interface, when using the 'Delete and Notify' option on a quarantined email, occasionally the notification would not contain a threat report.

The following is a list of frequently asked questions. The questions are categorized as follows: Pre-installation Installation and Configuration Troubleshooting Pre-installation How does GFI MailSecurity retrieve and count users? Should I install GFI MailSecurity in VS API or Gateway mode? What are the System requirements for GFI MailSecurity? Installation and Configuration How to configure IIS to use HTTPs for the GFI MailSecurity configuration Troubleshooting

The following patches have been released for GFI MailSecurity (build 20090526) Notes: Unless otherwise specified, all patches listed in this article will be included in newer builds of GFI MailSecurity. Installation instructions are included with the download. Patch: MSEC10PATCH2009061901

Description: This patch fixes an issue whereby folding of the MIME recipients may fail and in some cases cause long lines to appear in the message headers.

Download Link: MSEC10PATCH2009061901.zip Last Updated: 14th July 2009

GFI ReportCenter 3.6 has been released and is available for download.

New features in GFI ReportCenter 3.6 include: Localization to German, Italian, Spanish and Russian Updated reporting rendering engine to Crystal Reports 12 Built on updated version of Microsoft .Net Framework: 2.0 Note: Old ReportPack applications compiled for ReportCenter 3.5 are compatible and will run under ReportCenter 3.6. Limitations: GFI ReportCenter 3.6 will not install on Microsoft Windows 2000. More details here

Download location: www.gfi.com/reportcenter36/download This build will also be downloaded automatically by any GFI ReportPack if the latest version of GFI ReportCenter is not installed.