Symantec Mail Security for Exchange 6.0 Release Notes

Article:TECH97591  |  Created: 2009-01-19  |  Updated: 2014-07-10  |  Article URL http://www.symantec.com/docs/TECH97591
Article Type
Technical Solution


Issue



Release Notes - Symantec Mail Security 6.0 for Microsoft Exchange

Build 6.0.13.302

GA Release Date -- September 21, 2011


 


Solution



Included in these release notes:
 

    • What's New in Symantec Mail Security for Microsoft Exchange 6.0
    • End of Life Support
    • Upgrade Notes
    • Upgrade Steps
    • Internationalization Support
    • Known Issues
    • Resolved Issues
    • Previous Builds

Whats new in Symantec Mail Security for Microsoft Exchange 6.0


    - Maintenance Release for Symantec Mail Security addressing various client reported issues.

Support Details

Version support status information


Upgrade Notes

Before you upgrade make sure your server meets the system requirements. For details read ‘System requirements for Symantec Information Foundation Mail Security for Microsoft Exchange 2000 Server/Server 2003.’

SMSMSE 6.x supports upgrades from Symantec Mail Security for Microsoft Exchange 4.6.x and higher. If you have version 4.5 or earlier you must uninstall that version and then install SMSMSE 6.x.
 


Upgrade Steps
 

    To upgrade to a newer version of Symantec Mail Security 6.x
    1. Back up the settings.
    2. Install the new version of Symantec Mail Security for Microsoft Exchange 6.x.
    3. Open the user interface and verify that your settings are still correct. If your settings are not correct import the settings you backed up earlier.

       

Internationalization Support

Known Issues

Resolved Issues

6.0.13.302

  • Autonomy KeyView - Several important defects were fixed in the KeyView filter component used by the attachment content filter module.

6.0.12.297


6.0.11.296
 

6.0.10.295
 


6.0.9.286

Symptom: Several important defects were fixed in the KeyView filter component used by the attachment content filter module.
Solution: KeyView filter used by attachment content filter module was upgraded to latest available version.

Symptom: Symantec Endpoint Protection fails to co-exist with Symantec Mail Security for Microsoft Exchange on 64-bit platform.
Solution: Fixed.

Symptom: Need to add an option to enable “Scan Now” on Exchange 2007 server.
Solution: Fixed.
User Interface: Added the menu option.
Messages: Added new events.

Symptom: Need to re-enable the CF integration with the Outbreak rule for subject line and attachment so as to automatically trigger detection in the case of an outbreak.
Solution: Fixed.
User Interface: Added the menu option.
Messages: Added new events.

Symptom: Log analysis shows memory leak when using Symantec Mail Security 6.0 for Microsoft Exchange.
Solution: Fixed.

Symptom: Error is received when the Symantec Mail Security for Microsoft Exchange console is used to push definitions to a group of servers.
Solution: Fixed. A new registry key named "ArchivalTimeOutInSeconds" is added to configure the timeout period in seconds.

Symptom: Error appears when emailing reports.
Solution: Fixed.
Messages: Added a new event log to indicate a failure encountered while sending email in the first attempt.

Symptom: Server name is not shown in the notification body text for all notifications that fall in the category of “service critical failures”.
Solution: Fixed. Server name is now appended at the end of the notification body text for all the notifications to be sent to the Administrator.
Messages: No new messages are added but existing notification email messages will now include the server name.

Symptom: Custom location for Quarantine folder is not being used and is being replaced with the default folder location.
Solution: Fixed.
Messages: A new event will be generated when Symantec Mail Security for Microsoft Exchange fails to quarantine a message.

Symptom: In certain scenarios, Symantec Mail Security for Microsoft Exchange catches emails as unscannable.
Solution: Fixed.

Symptom: Need to add text that asks users to press F5 to see license status on the Global Group (and any sub-group) on the Monitor tab.
Solution: Fixed.
User Interface: Modified user interface to reflect the change. Added the following text to the Monitors > Server Status > Server Status Heading page: "Server Status (Press F5 to view the status of all servers within the group)".

Symptom: Brightmail error (Event ID 514) shows up in the event log after enabling the Symantec Premium AntiSpam on Windows Server 2008.
Solution: Fixed.

Symptom: Need to add SCC Cluster resource configuration information for Windows Server 2008.
Solution: Updated the corresponding Implementation Guide.

Symptom: Need to update context sensitive help for 6.0.9 release.
Solution: Updated the context sensitive help.

Symptom: Need to modify the Readme file for 6.0.9 release.
Solution: Modified the Readme file.

Symptom: Need to update the Implementation Guide of Symantec Mail Security for Microsoft Exchange Server 2007 for 6.0.9 release.
Solution: Updated the corresponding Implementation Guide.

Symptom: Need to update the Implementation Guide of Symantec Mail Security for Microsoft Exchange Servers 2000 and 2003 for 6.0.9 release.
Solution: Updated the corresponding Implementation Guide.

Symptom: Need to update the Getting Started Guide of Symantec Mail Security for Microsoft Exchange for 6.0.9 release.
Solution: Updated the Getting Started Guide.

Symptom: Need to change the copyright year to 2009 throughout documentation.
Solution: Fixed the Help and the Implementation Guides.


6.0.8.262

This release of Symantec Mail Security for Microsoft Exchange has been certified on Windows Small Business Server 2008.

Symptom: Several defects were fixed in the KeyView filter component used by the attachment content filter module.
Solution: Upgraded KeyView filter to the latest available version.

Symptom: Upgrade Symantec Premium AntiSpam component to the latest version.
Solution: Fixed.

Symptom: Need to add a checkbox in the GUI for file filtering based on filenames so as to bypass scanning of container files.
Solution: Modified the source code to introduce a checkbox in the GUI.
User Interface: Added a new checkbox "Bypass scanning of container file(s)" in the GUI.

Symptom: Files larger than 5MB that contain characters from Korean, Thai, Malaysian, and Standard Chinese are caught as unscannable.
Solution: Fixed.

Symptom: SAVFMSECtrl.exe quits unexpectedly.
Solution: Fixed.

Symptom: Require updating of the inline Help and Implementation Guide. A new checkbox with the text "Bypass scanning of container file(s)" is added in the GUI of Symantec Mail Security for Microsoft Exchange.
Solution: Updated the inline Help and Implementation Guide accordingly.

Symptom: Require updating of the inline Help and Implementation Guide with information regarding Scheduled Consolidated Reports.
Solution: Updated the inline Help and Implementation Guide accordingly.

Symptom: Require updating of the Implementation Guide for Mail Security for Exchange 2007. The Implementation Guide needs to specify which Exchange server roles are required to license and enable Symantec Premium AntiSpam on Exchange 2007.
Solution: Updated the Implementation Guide for Mail Security for Microsoft Exchange 2007 accordingly.


6.0.7.253

Symptom: Support for advanced Veritas Cluster Server (VCS) configurations.
Solution: In Symantec Mail Security 6.0.7 for Microsoft Exchange (SMSMSE 6.0.7), multiple virtual Exchange servers are supported in a single cluster. The following advanced VCS configurations are now supported:
 

    Active/Passive N to 1
    Active/Passive N + 1
    Active/Passive N to N (or Any-to-Any configuration)

    Note:
    1. SMSMSE 6.0.7 supports VCS 5.0 with the latest service patch and VCS 5.1.
    2. VCS version 4.3 support is removed in SMSMSE 6.0.7.
    3. Windows 2000 is supported only with one Exchange Service Group. Other configurations like N to 1, N + 1, and Any-to-Any are not supported.


Symptom: Quarantine notification includes the original HTML/RTF text message.
Solution: Fixed.

Symptom: Enhancement for monitoring SMSMSE Utility service
Solution: In SMSMSE 6.0.7, whenever the Utility service stops running, SMSMSE sends email notification to administrator(s) and puts warning message into Windows event log. The email notification and event log message get generated after every six hours until the Utility service is restored.
The notification can be managed by adding a registry key ‘UtilitySrvNotificationBool’ (of type DWORD) under \SMSMSE\6.0\Server\Components\SMTP. Setting its value to 0/1 will disable/enable the notification, respectively.
Messages: A new warning message (Event ID = 391) is generated into Windows event log to indicate that the Utility service is offline.

Symptom: Cluster resources fail to register on German OS.
Solution: Fixed.

Symptom: A fatal error is generated and the console closes when adding an additional Exchange Server to the Management Group in Exchange Server 2007 SP1.
Solution: Fixed.

Symptom: A corrupted file causes an error in Symantec Mail Security Managed Components and the list of Quarantined items displayed in the GUI is either blank or truncated.
Solution: Fixed.

Symptom: SMSMSESMTPAgent times out.
Solution: Fixed.

Symptom: SMSMSE 5 displays an infected message's originating email while SMSMSE 6 only displays "Unknown Sender."
Solution: Fixed. If the sender name is not available, SMSMSE 6.0.7 will use sender's SMTP address to show as sender name in reports.

Symptom: Integrate LU Admin 2.1.3 with the CD.
Solution: Replaced LU Admin 1.5.7 with 2.1.3 on the CD.

Symptom: Update documentation regarding new enhancement for VCS support.
Solution: Getting Started Guide and Implementation Guides are updated accordingly.

Symptom: Update documentation regarding LUA integration.
Solution: Getting Started Guide and Implementation Guides are updated to refer to the latest version of LiveUpdate Administrator.

Symptom: Update documentation to change Spam Stats Manager service to Utility service.
Solution: Implementation Guides are updated accordingly.


6.0.6.235

Symptom: Error message 'Failed to enable ASP.NET web extensions. Installation will not continue.' appears while installing SMSMSE on a computer running Windows Server 2008 with Exchange 2007.
Solution: Install IIS role correctly. It is required to select all features of IIS to install SMSMSE.

Symptom: When the console starts, there is no option to turn on/off automatic login to all the servers in a group.
Solution: Added new option.
User Interface: A new option is added in ‘Asset Management’ page for automatic login to all servers in a group. Additionally, if automatic login is off, a message box is provided for asking if Mail Security should connect to all servers in a group as a part of manual refresh.

Symptom: Spam is rejected with SMTP code ‘550 5.7.1’
Solution: Fixed.

Symptom: ‘Allow only attachment rule’ is not removed from the list of default content filtering rules.
Solution: This rule is available only if Mail Security is upgraded from a previous version. After a clean installation of Mail Security 6.0.6 this rule is not visible.
User Interface: This rule is removed from the Content Filtering Rules page.

Symptom: Performance log fails to start with SMSMSE counters.
Solution: Fixed.

Symptom: There is no option to increase the frequency of virus definition updates.
Solution: Added new options.
User Interface: Added two more time intervals in the user interface – 15 minutes and 30 minutes.

Symptom: Cluster failover results from SAVFMSECtrl communication failure and SAVFMSESp restart.
Solution: Fixed.

Symptom: ‘Run Rapid Release Definitions’ does not work on Windows Server 2008.
Solution: Updated the section 'Prerequisite for Windows Server 2008' in README file.

Symptom: Installing SMSMSE 6.0 with an account, which has Enterprise Admin as the primary group, causes problems.
Solution: Modified the source to retain the previous Owner and Group of the CustomSD. Thus, if the initial value of CustomSD registry key is correct, the modified value will also be correct.

Symptom: Symantec Premium AntiSpam does not work on non-English Operating Systems.
Solution: Fixed.

Symptom: Information Store service fails on a clustered Microsoft Exchange server.
Solution: This issue is on Microsoft Exchange, and not on SMSMSE. Apply the following hotfixes from Microsoft to resolve this issue:
http://support.microsoft.com/kb/914394
http://support.microsoft.com/kb/941060

Symptom: License file location on Windows Server 2008 systems is different.
Solution: Updated the Implementation Guide accordingly.

Symptom: The new option to turn on/off automatic login to all servers in a group on console start is not documented.
Solution: Updated the Help and Implementation Guide accordingly.

Symptom: The newly added option to increase the frequency of virus definition is not documented.
Solution: Updated the Help and Implementation Guide accordingly.

Symptom: ‘Allow only attachment rule’ is removed from the list of default Content Filtering rules.
Solution: Updated the Help and Implementation Guide accordingly.

Symptom: New supported platforms are added to Server and Console requirements.
Solution: Updated the Implementation Guide accordingly.

Symptom: Notification variable is used only for quarantine threshold notification and is not applicable to all ‘Rule violation notifications’.
Solution: Updated the Help and Implementation Guide accordingly.

Symptom: Clicking on ‘Update Version Status...’ does not download and install the VS package.
Solution: Fixed. However, earlier versions of Mail Security (prior to 6.0.5) will not be able to download VSPs.


6.0.5.218

Note: SMSMSE 6.0.5.218 is certified against Exchange 2007 SP1 and SMSMSE 6.0.5 Console is certified against Vista 32 bit.

Symptom: Several important defects were fixed in the KeyView filter component used by the attachment content filter module.
Solution: KeyView filter was upgraded to latest available version.

Symptom: The Savfmselog.exe process caused a memory leak.
Solution: Fixed.

Symptom: SMSMSE 6.0.3.201 does not repair Office format files.
Solution: The relevant module was upgraded to the latest available version.

Symptom: SMSMSE Definitions are corrupted when used with a SAVCE managed client.
Solution: When AV engine initialization fails, it will attempt to update virus definitions from Symantec's shared virus definition location. If there are no good definitions in the shared location, it will attempt to perform a LiveUpdate, provided LiveUpdate is enabled in the system and the content license is valid.

Symptom: If the Task Scheduler Service is not running then SMSMSE service fails to start.
Solution: SMSMSE allows users to save changes to scheduled tasks like Scheduled reports, scans or LiveUpdate even if the Windows Task Scheduler service is not running. However, the Windows Task Scheduler Service must be running to run these scheduled tasks. When the user saves changes to settings of such tasks while the Windows Task Scheduler is not running, a warning message stating that SMSMSE cannot run that scheduled task will be shown to the end user.

Symptom: Unable to release multiple items from Quarantine by mail.
Solution: Fixed.

Symptom: After installing SIFMSMSE 6.0 to 2003 SBS, Dredger.exe crashes, faulting module MSjetOLE.
Solution: Fixed.

Symptom: Runtime Error: Microsoft Visual C++ Runtime Library in SAVFMSEJM.EXE during a scheduled scan
Solution: Fixed.

Symptom: XLS file is unscannable in SMSMSE 5 and 6. Symantec AntiVirus scans them without any problem.
Solution: Upgraded the scanning component.

Symptom: Registry write failure for Auto-protect.
Solution: Fixed.

Symptom: Unable to set Spam Scoring to 80.
Solution: Fixed.

Also updated in this release:
Readme.txt
Implementation Guide
Getting Started Guide
LU Admin implementation Guide
Management Pack Integration Guide
Online Help


6.0.4.209
Symptom: Multiple defects were fixed in the KeyView Filter component.
Solution: KeyView Filter component, which is used by attachment content filter module, has been upgraded to the latest available version.


BUILD 6.0.3.201

Symptom: Inaccurate console display when logged in as member of the SMSMSE Viewers Group.
Solution: Corrected in new build.

Symptom: Can't bring the SMSMSEVCSClusterResource online on Windows2003 32bit with Exchange2003.
Solution: Corrected in new build.

Symptom: Native Exchange 2007 content filtering fails when SMSMSE 6.0 is installed on the Hub
Solution: Corrected in new build.

Symptom: VSP package is not working. Clicking on the button "Update Version status..." does not download and install the VS package.
Solution: This is a known issue. Update via Version Support Package feature (VSP) will not be available for SMSMSE 6.0.3.


6.0.2.198

Symptom: SMSMSE 6.0 does not support E12 on VCS 5.0.
Solution: Corrected in new build. While installing SMSME 6.0 product on 64bit platform and if VCS is installed, the installer shall prompt the user to install and register SMSMSE resource for VCS. The product uninstallation shall prompt the user to unregister and uninstall SMSMSE resource for VCS.

Symptom: Install error when computer name is put in for notification email address.
Solution: Corrected in new build.

Symptom: VSP package is not working. Clicking on the button "Update Version status..." does not download and install the VS package.
Solution: Corrected in new build.


BUILD 6.0.1.189

Symptom: Inetinfo crashing on certain message content when SMTP content filtering is enabled
Solution: Corrected in new build.





 



Legacy ID



2009111914013154


Article URL http://www.symantec.com/docs/TECH97591


Terms of use for this information are found in Legal Notices