MailMarshal SMTP 2006

Version: 6.2.2, Last Revision: September 07, 2007

These notes are additional to the MailMarshal User Guide and supersede information supplied in that Guide.

The information in this document is current as of the date of publication. To check for any later information, please see Marshal Knowledge Base article Q11589.

Table of Contents

What's New
Upgrading MailMarshal
Uninstalling
Hardware and Software Requirements
Change History

 

What's New

For more information about additional minor features and bug fixes, see the change history.

Features New in 6.2

Features New in 6.1.8

Features New in 6.1.6

Notes:

Features New in MailMarshal SMTP 2006

MailMarshal SMTP 2006 delivers a range of new security enhancements designed to protect your organization against current and future email threats.

SECURITY | Zero-Day Attack Protection
Allows Marshal to provide new security updates to your MailMarshal server(s) with same-day efficiency. When new email threats are detected by Marshal’s Threat Team, Marshal can release “zero-day” updates to secure your MailMarshal server automatically. This not only provides rapid response security but reduces administration for your organization. Zero-Day attack protection is a key part of Marshal’s “set & forget” ethos – Marshal can identify new spam, virus or other email exploits and ensure that your email network remains secure and protected.

SECURITY | DOS Gateway Protection
A Denial of Service (DOS) attack on an email server involves rapidly ‘flooding’ the server with continuous email connections. The end effect is that the email server is overwhelmed by the sheer volume of email connections. This type of attack results in your organization either experiencing dramatically reduced email service or being deprived of email all-together. Naturally, this can be catastrophic for many organizations that depend on email.

DOS Gateway Protection in MailMarshal SMTP 2006 is designed to look for unusual email activity that indicates a potential DOS attack, such as multiple, rapid connection attempts from a single IP address. MailMarshal then automatically escalates preventative measures depending on the nature of the anomalous activity: from throttling back response times, to dropping the connection and blocking the offending IP address for a period. This provides your organization with substantial DOS protection. In the event that one of your customers’ servers is commandeered by a spammer and your organization is attacked, MailMarshal will take steps to manage the attack. MailMarshal will then automatically resume normal service with your customer’s email system, once the attack has passed.
SECURITY | DHA Gateway Protection
A Directory Harvesting Attack (DHA) is a malicious activity usually employed by Spammers to ‘harvest’ valid email addresses from an email server. This can sometimes explain why a new email address may receive spam within days of being activated. DHAs involve a systematic approach, trying different combinations of email addresses to determine which addresses the target server considers valid or invalid. MailMarshal SMTP 2006 can detect the patterns of these systematic harvesting techniques and take appropriate action, including denying connections from the attacking server. This ultimately results in your organization being sent less spam and denying spammers access to your organization's valid email address list.

SECURITY | TLS Encryption
Transport Layer Security is a method of email encryption that allows two servers to create a secure SMTP connection between them. TLS is effectively SSL for SMTP email connections and ensures that any communications between two TLS enabled servers remain private and confidential. TLS is easy and cost effective to establish, providing an ideal way for organizations to communicate securely.

ANTI-SPAM | Spam Categories
MailMarshal SMTP 2006 can sort spam into related categories such as Adult, Health, Stocks, Financial and Phishing. This allows your organization to apply different polices to different types of spam. For example, you may choose to quarantine Health and Financial spam for your employees to manage directly via the SQM system (Spam Quarantine Management). Conversely, you may choose to delete Adult and Phishing spam automatically without exposing end users to such spam. Spam Categories also allow you to report on and analyze the types of spam that your organization receives. This may help you fine-tune your anti-spam polices to be more effective.
 
ANTI-SPAM | CountryCensor
MailMarshal employs a multi-faceted approach to anti-spam, utilizing a range of technologies to analyze messages and identify spam and other threats. CountryCensor is one of the latest technologies available in MailMarshal SMTP 2006. CountryCensor identifies the country that an email message has originated from allowing you to apply whatever policy you desire. For example, your business may be entirely locally focused, only dealing with suppliers and customers from within your own country. As a result, you may choose to simply deny any email message that does not originate from within your own country. Another use may be to apply different policies to messages from different countries, such as making anti-spam rules more stringent for emails that originate from some countries than from others. CountryCensor also allows you to classify, and then report on, which countries you receive email from and monitor changes in those trends over time.

ANTI-SPAM, ANTI-PHISHING | URLCensor
As with CountryCensor, URLCensor is another method that MailMarshal uses to examine email messages and determine any potential security risk. URLCensor specifically examines URLs that may be included in an email and references them against a real-time blacklist of known spam and phishing web sites. These real-time blacklists or RBLs are maintained by independent third parties. MailMarshal can be configured to utilize more than one RBL, making for improved accuracy and security. If a message contains a URL that is listed on a RBL, MailMarshal can quarantine the message automatically.

ANTI-VIRUS | Norman Sandbox Support
Norman is a third party anti-virus (AV) vendor (one of many that Marshal supports). Standard AV solutions use virus signatures files that are created when a new virus appears in the wild. This requires that the AV solution is regularly updated to keep it current with the latest virus threats. Norman’s sandbox technology is specifically designed to identify potential viruses that have not been seen before. The concept is that if an unknown executable file type is encountered, the sandbox feature will place the file into a secured, safe environment and allow the file to execute. Norman then monitors the behavior of the file to determine whether it exhibits any potentially malicious characteristics. If the file’s activity appears to be safe, it will allow the file to pass. If on the other hand the file’s activity is malicious, the scanner will treat it like a virus and take quarantine action. The Norman Sandbox feature can not only detect viruses but also spyware applications or other malicious files. MailMarshal SMTP 2006 directly supports the Norman Sandbox feature, allowing you to scan email messages with unknown attachments in real-time. You can learn more about the sandbox technology at the Norman web site - http://www.norman.com/Virus/Sandbox/en-us
SECURITY | HELO SMTP Receiver Support
MailMarshal has two general methods of applying security policies – Receiver Rules and Standard Rules. Standard Rules can apply a wide range of policies to email messages that have been received by MailMarshal. Receiver Rules are used to reject email messages before they are even received. For example, if you want to block messages that are bigger than a defined size limit, receiver rules can identify oversized messages when the sending server first tries to establish a connection. This ensures that your bandwidth is protected – the key reason for placing a size limit on messages in the first place.

HELO refers to the very first messages that are transferred between SMTP email servers when trying to establish a connection, before sending an email. HELO strings identify the email server and provide properties about that server and what it wants. HELO support can allow MailMarshal SMTP 2006 to force a connecting email gateway to adhere to the industry standard SMTP connection process. This may include requiring the connecting email gateway to provide a Fully Qualified Domain Name (FQDN). This process has benefits in blocking spam. Spammers do not normally adhere to the HELO standards, often failing to provide a FQDN. This means that MailMarshal can apply different policies to email servers that do not match the HELO standards, such as refusing connections all together.
 

 

Upgrading MailMarshal

MailMarshal SMTP 2006 supports a direct upgrade from MailMarshal SMTP 5.5 and later versions. 

Please review the MailMarshal User Guide before upgrading.

For general information about upgrading issues see the remainder of this section.

Full details about upgrading from specific versions can be found in the following Marshal Knowledge Base articles:

To upgrade from a version prior to 5.5, first upgrade to version 5.5.

 

Changes in Database Structure and Prerequisites

MailMarshal SMTP 2006 requires a database to store configuration and logging data. If upgrading from MailMarshal SMTP 5.5 you will need to create a new database during the upgrade process and migrate existing data as a separate process.

MailMarshal can use:

The MailMarshal CD-ROM includes MSDE 2000 A (with Service Pack 3a), and Service Pack 3 for SQL 2000.

Upgrading a Single Server

To upgrade a single MailMarshal SMTP server from version 5.5 or above, install the new version over your existing version. You do not need to uninstall your existing version. During installation, specify a new database location.

If your existing installation uses MSDE 1.0 on the MailMarshal SMTP server, the upgrade installation will offer to upgrade MSDE.  If your existing installation does not use a database, you can install MSDE 2000 on the MailMarshal SMTP server during installation. For more information about selecting the appropriate SQL software and the appropriate installation location, see the MailMarshal User Guide.

Upgrading an Array of Servers

If you have configured an array of MailMarshal SMTP 5.5 servers, please review Q11025: Upgrading from MailMarshal 5.5 to MailMarshal SMTP 2006

Upgrading a MailMarshal SMTP Secure Server

MailMarshal SMTP 2006 does not support MailMarshal Secure (S/MIME). Before upgrading you must remove the MailMarshal Secure component using the Add/Remove Programs control panel. To remove this component from a MailMarshal SMTP 4.2.5 installation, first upgrade to version 5.5 then remove the component.

Notes on Upgrading

Note: The information in this document is current as of the date of publication. To check for any later information, please see Marshal Knowledge Base article Q11589.

 

Uninstalling

MailMarshal can be installed in a variety of scenarios. For full information on uninstalling MailMarshal from a production environment, see the MailMarshal SMTP User Guide.

To uninstall a trial installation on a single computer:

  1. Close all instances of the MailMarshal Configurator, MailMarshal Console, and MailMarshal Reports.
  2. Use Add/Remove Programs from the Windows Control Panel to remove MailMarshal SMTP.
  3. Use Add/Remove Programs from the Windows Control Panel to remove additional components you may have installed, such as Web components or Reports.
  4. If you have installed any components (such as the Configurator, Console, Web components, or Reports) on other computers, uninstall them.
  5. If you have installed MSDE specifically to support MailMarshal and no other applications are using it, uninstall MSDE.

 

Hardware and Software Requirements

The following system requirements are the minimum levels required for a typical single-computer installation of the MailMarshal SMTP Server, Array Manager, and selected database. If you install MailMarshal SMTP on an existing email server, the minimum hardware requirements may be greater than those shown in the table, depending on the number of users and typical email volume.

Category
Requirements
Processor
Pentium 4
Disk Space
10GB (NTFS)
Memory
512MB
Supported Operating System
  • Windows 2000 Professional, Server or Advanced Server Service Pack 4 or later (with latest security updates)
  • Windows Server Standard or Enterprise 2003 with or without Service Pack 1 (with latest security updates)
  • Windows XP Professional Service Pack Service Pack 1 or Service Pack 2 as a domain member (with latest security updates)
Notes:
  • MailMarshal SMTP does not support 64-bit versions of Windows.
  • MailMarshal SMTP Server does not run on Windows XP Professional if the computer is not a domain member. If a MailMarshal SMTP Server in a DMZ is not a domain member, ensure the computer is running a supported version of Windows 2000 Server or Windows Server 2003.
Network Access
  • TCP/IP protocol
  • Domain structure
  • External DNS name resolution - DNS MX record to allow MailMarshal SMTP Server to receive inbound email
  • If installed on existing email server: Localhost IP address 127.0.0.1 on port 25
Software
  • Database server: MSDE 2000 Service Pack 3a or later, SQL 2005 Express, Microsoft SQL Server 2000 Service Pack 3a or later, or SQL Server 2005
  • Microsoft Data Access Components (MDAC) 2.7 or if using named database instances, MDAC 2.8.
  • Antivirus scanning software supported by MailMarshal SMTP.
Port Access
  • Port 25 - Inbound SMTP and to email servers
  • Port 53 - for DNS external email server name resolution
  • Port 80 (HTTP) and Port 443 (HTTPS) - for SpamCensor updates
  • Port 1433 - for connection to SQL Server database and Reports console computers
  • If installed on an existing email server: Port 97 or another available port - for email transfer from MailMarshal SMTP
  • If serving as a POP3 email server: Port 110 - for email transfer to POP3 mailboxes

 

Change History       

The following additional items have been changed or updated in the specific build versions of MailMarshal SMTP listed.

Note: The information in this document is current as of the date of publication. To check for any later information, please see Marshal Knowledge Base article Q11589.

6.2.2 (September 07, 2007)

MM-911 The TAR unpacker included in MailMarshal was vulnerable to Directory Traversal Attacks. Fixed.

6.2.1.3252 (May 2, 2007)

MM-730 A buffer overrun in the cached DNS framework could cause the Receiver to stop unexpectedly. Fixed.
MM-731 The Spam Quarantine Management website password reset facility was vulnerable to a specially crafted request. This vulnerability could allow the new password to be sent to arbitrary additional email addresses. Fixed.
MM-732 A problem with PDF checking could cause email containing valid PDF files to be deadlettered. Fixed.
MM-781 Receiver Rule logging could cause database deadlock errors. The issue has been addressed by batching the insertion of these records.

6.2.0.2977 (May 2, 2007)

MM-181 Unpacked files with Unicode or non-English characters in the long file names could not be scanned. 8.3 filenames are now used to access these files.
MM-260 DoS and DHA were not creating logging entries. Fixed.
MM-363 PDF unpacking could cause the MailMarshal Engine to stop. Fixed.
MM-365 Some characters were not displaying correctly in the Configurator when entered in the classification description. Fixed.
MM-367 MailMarshal did not generate an error if semi-colons were not used between entries in the TO, CC and BCC fields in message templates, or if multiple variables were entered into the From field. Fixed.
MM-369 DNS lookup and result caching is now provided by the Controller.
MM-373 Additional configuration is available per node for Receiver binding. Thread usage limits can be set for specific IP addresses or ports.
MM-375 Database stored procedures and indexes have been modified to improve performance at large sites.
MM-376 Modified the PurgeMessages stored procedures to improve performance under heavy load.
MM-394 DoS logging appeared in the MMReceiver logs regardless of whether or not DoS was enabled.
MM-395 Some TNEF files were not being recognized correctly. Fixed.
MM-396 The number of dump files the MailMarshal services generate is now limited to 10.
MM-397 Rule Merge files now can only be imported to the correct version of MailMarshal.
MM-407

LDAP groups were not fully populated if the connection to the LDAP server was terminated in the middle of an update. Fixed.
MM-408 DHA evaluation was being performed for outbound messages. Fixed.
MM-409 A Registry entry has been added to control whether invalid recipients are stripped by DHA evaluation.
MM-411 The node properties dialog did not correctly show the status of the Customized Local Domains checkbox. Fixed.
MM-417 Remote Console users were not permitted access as specified in MailMarshal security settings unless they had administrative rights on the server. Fixed.
MM-420 The Array Manager could fail to process a mail file because the file was opened for writing by another process. Fixed.
MM-425 Large sites received "Cannot create new connection because in manual or distributed mode" errors, when using Receiver rule logging. Fixed.
MM-427 Users could create and use a Standard folder while editing a Parking rule action. This caused the Engine to stop. Fixed.
MM-429 A problem with the XML configuration handler could cause the Controller to stop unexpectedly. Fixed.
MM-432 The standalone Message Viewer now uses the Windows theme.
MM-433 LDAP and AD groups could not be directly specified in the DHA group selection due to unescaped commas. Fixed.
MM-434 ORDB has been removed from the default list of Blacklists, because ORDB has shut down.
MM-439 The selection list for server notification templates included digest templates. Fixed. Where digest templates were used, upgrade selects the built-in template.
MM-440 Receiver HELO rules now allow wildcards.
MM-443 User Safe and Blocked senders lists in the SQM console now allow additional wildcards.
MM-454 Some PDF documents were not being recognized as encrypted. Fixed.
MM-457 The PDF unpacker was taking an excessive amount of time while extracting certain individual pages. Fixed.
MM-464 Local Domain entry now supports the standard wildcard syntax including character ranges.
MM-467 The proxy configuration option 'Preset Configuration' has been removed. Upgrades change 'Preset Configuration' to 'Direct Access.'
MM-468 DNS Blacklist evaluation has been enhanced to support the range of responses provided by Spamhaus ZEN. For more information about ZEN, see Marshal Knowledge Base article 11541.
MM-469 Searching by Message Name could be slow. An index hint has been added to improve performance.
MM-471 Digest generation performance has been improved.
MM-476 The Console could become unresponsive while releasing messages due to problems checking Windows access rights. Fixed.
MM-477 On some occasions the file name condition wasn't triggering with obfuscated headers. Fixed.
MM-486 MailMarshal can now detect Word documents saved in Office 2003 format, by Office 2007 applications. (NOTE: At this point MailMarshal does not fully support Office 2007 documents.)
MM-490 Updated OpenSSL libraries to the most recent version, due to earlier versions containing security vulnerabilities.    
MM-492 Certain non-conforming subject lines could be incorrectly converted from UTF7 to Unicode. Fixed.
MM-493 Stipulated DoS and DHA blocking periods were not being honored. Fixed.
MM-514 Improved DOS and DHA logging in Receiver log.
MM-517 It is now possible to specify which protocol is used during TLS sessions by adding a Registry entry. SSLv23 is the default.
MM-520 Message digests now correctly display subject lines containing Unicode characters.
MM-536 McAfee for Marshal dll has been updated to use McAfee engine 5.100.
MM-546 The Console generated numerous error dialogs if services on a node were stopped while the node was selected. Fixed. 
MM-564 The CountryCensor database has been updated to a more recent version.
MM-569 CountryCensor XML files have been updated to use the new entries in the CountryCensor database.

6.1.8.2172 (November 20, 2006)

MM-288 The New Rules Merge file for a release is now included in the installation.
MM-400 DOS and DHA exclusion for a remote server was ignored if the server issued a RSET command. Fixed.
MM-401 Customizing Local Domain information on a node could cause configuration issues when upgrading. Fixed.
MM-405 LDAP search roots using an initial * to retrieve an OU, or containing only DC entries, could cause an error. Fixed.

6.1.8.2137 (November 13, 2006)

MM-383 In build 6.1.8.2074, Web Consoles did not run under Windows 2000 due to a problem with a DLL dependency. Fixed.
MM-384 After upgrade to 6.1.8.2074, the MailMarshal Sender could fail to start if forwarding host delivery was specified. Fixed.
MM-398 Database log files on standalone email processing servers were not correctly processed by the upgrade routines. Fixed.

6.1.8.2074 (November 03, 2006)

MM-8 LDAP or Active Directory group names over 100 characters long were truncated. Fixed: the new limit is 512 characters.
MM-9 Version number added to start up log and can now be seen during start up messages.
MM-18 A registry key can be set to enable logging of SpamCensor results with zero score. Contact Marshal Technical Support for details.
MM-26 Unpacking of PDF text with font encodings has been improved.
MM-45 Configurations from earlier versions of MailMarshal could not be imported successfully to MailMarshal 2006. Fixed.
MM-48 When delivering messages externally, MX records with the same priority were not used alternately. Fixed.
MM-50 Changes to local domains no longer require service restart.
MM-65 Upgrade from an installation originally installed as version 5.5 could cause error upgrading POP3 accounts. Fixed.
MM-115 Apple Single files could be blocked as double extensions, due to the naming convention for these files. Fixed.
MM-126 MailMarshal is now RFC compliant in regards to the storage of email addresses and domain names in the database.
MM-135 The Recipient variable was not correctly populated when multiple BCC recipients were specified. Fixed.
MM-137 Redirection vulnerability in spam management website. Fixed.
MM-149 The grand totals for Email Traffic reports were not correct. Fixed.
MM-151 A directory traversal exploit vulnerability was present when unpacking ARJ files (reference ZDI-CAN-003). Fixed. For more information, see Marshal Knowledge Base article Q11450.
MM-152 Users can now select which groups they use for DHA.
MM-160 Improvements have been made to the upgrade process and logging, related to configuration upgrade and restarting Array Manager.
MM-162

Folder Retention can now be set to over 36 years or 430 months, without causing the MailMarshal folder in the console to produce an error when clicked on.
MM-164 Incorrect unpacked RTF file size. Fixed.
MM-165 The console could exit unexpectedly when viewing messages with attached Microsoft Office documents, due to a buffer overrun. Fixed.
MM-170 Image Analyzer crash due to invalid image format resolved. Images now treated as being an "unsupported format"
MM-174 Console message search now allows full message names, so messages on a specific server can be searched for.
MM-179 PDF documents embedded within PowerPoint files were recognized as WMF due to an unpacking error, and were not being scanned properly. Fixed.
MM-180 Log error messages for the SpamCensor updater have been improved.
MM-182 Image Analyzer Example rules added to 'Sample rules'.
MM-188 Folder retention period is less than or equal to 99 years, however error message given when trying to create a retention period over that time stated folder retention needs to be less than 99 years. Fixed.
MM-190 TextCensor export did not allow selection of file type if Windows was set to hide file extensions for known types. Fixed.
MM-197 Some Microsoft Excel files were incorrectly recognized as OLE. Fixed.
MM-198 MailMarshal Engine had a virtual memory leak when using fingerprints. Fixed.
MM-203 A registry key can be set to alter the base URL for Spam Quarantine Management release links. Contact Marshal Technical Support for details.
MM-205 MailMarshal now checks for SpamCensor updates hourly, allowing enhanced Zero Day response.
MM-212 TextCensor could mis-interpret "words" in the text of PDF documents due to incorrectly extracted text. Fixed.
MM-227 The default template for Lotus Domino LDAP connection has been improved.
MM-228 Text has now been added to the received line to indicate message was received using TLS.
MM-230 Issues when moving quarantine folder location with the Server tool. Fixed. 
MM-236 Group selection window now has scroll bar so entire domain component can be seen when choosing user groups.
MM-237 Some winmail.dat files were not properly unpacked. Fixed.
MM-239 Validation of email addresses for login to Spam Quarantine Management now allows additional characters that are valid for SMTP email addresses.
MM-241 A stand-alone viewer for MML files is now included in the installation.
MM-242 Consoles now show multiple MX records, priority, and the last error message that happened for the domain.
MM-245 Upgrade from an installation originally installed as version 5.5 could fail with a DHA configuration error. Fixed.
MM-261 POP3 account validation again allows certain special characters that were available in MailMarshal 6.0 but removed in 6.1
MM-272 Reporting on messages with very long domain names has been improved.
MM-275 On upgrade, attempts to restart services that are already running now do not generate a warning window.
MM-295 Uninstallation did not remove the Installtype registry value. Fixed.
MM-316 PestPatrol signature updates were not applied automatically, and required manual reload. Fixed.
MM-339 The default CountryCensor IP database has been updated.
MM-340 Deadletter notifications can be disabled by setting the template to None. This feature is intended to be used when deadletter messages are digested.
MM-343 Image Analyzer could fail on specific corrupt GIF files. Fixed.
MM-344 Classification Detail by Local Domains report incorrectly showed temporary delivery failures (421) as failure due to TLS. Fixed.

6.1.6 (July 12, 2006)

MM-32 ACE files are now unpacked by MailMarshal.
MM-66 A Registry entry has been added to allow sending of deadletter notifications for MalformedMime messages.
MM-67 In some cases (particularly in cluster installations) MailMarshal Controller could exit unexpectedly during startup or shutdown. Fixed.
MM-74 The DOS/DHA exclusion list was not being applied to DHA configuration. Fixed.
MM-89 The CreditCard.xml SpamCensor configuration file contained an incorrect reference and was never applied. Fixed.
MM-94 Deleting a local domain now raises a confirmation dialog.
MM-96 External command return code configuration did not treat ranges correctly. The starting and ending numbers in the range were excluded (for instance 1-5 matched 2, 3, and 4 only). Fixed: starting and ending numbers are included (1-5 now matches 1, 2, 3, 4 and 5).
MM-97 Renaming a group referenced by an "add message users into group" rule action caused the MailMarshal Engine to be unable to start. Fixed.
MM-132 Upgrade failed when Microsoft XML Parser 3.0 was not present. The installer now enforces the stated prerequisite of MDAC 2.7, which includes Microsoft XML Parser 3.0.

6.1.5 (May 24, 2006)

MM-33 Using TLS could cause Windows Socket errors if another exception was raised during Receiver processing. Fixed.
MM-35 The Message Release external command (MMReleaseMessage.exe) now accepts authentication options on the command line (useful under Windows Server 2003 Enhanced Security Configuration).
MM-43 Sophos integration could fail to re-initialize if definitions were updated while email was being processed. Fixed.
MM-44 Configuration import now only accepts configurations that match the current software version.
MM-64 Importing a signed certificate through the TLS Wizard without specifying a private key could cause earlier private key data to be lost. Fixed.

6.1.4 (April 10, 2006)

MM-27 License keys have reverted to MailMarshal SMTP 6.0 format, not version 6.1.3 format.
165395 When accessing message details in the Web Console, all tabs have consistent backgrounds.
165545 The Web Console Alter History page now includes a Refresh button.
165869 Search options have been removed from the right-click menu for messages because they are not applicable.
165931 Console search pane scrolling has been corrected.
166026 POP3 account creation now checks for invalid characters in the user name.
166237 Previous and Next page buttons in Web Console Message History now have titles.
166304 Display of destination IP address format in the Web Console has been corrected.
174082 For RFC compliance, the Message Stamp editor requires breaks in lines with over 1000 characters.
174772 Terminology in Sender and Receiver logs has been standardized using RX: and TX:.
177035 Folder colors in the Console are now consistent when viewed with low color.
184411 Display of DOS and DHS information on the Today Page has been improved.
184988 The setting of the Count Identical Messages parameter has been added to the title of reports where applicable.
185163 Formatting of the report Email Traffic Summary by Selected Domain has been improved.
185304 Formatting of the report Senders Blocked by DHA Prevention has been improved.
185320 Options and display for the Quarantine Folder Action report have been clarified.
187449 Paging of the report Classification by Selected User has been made consistent with other reports.
187574 Unused SQL related items were removed from the performance monitor counters.
187663 The Console and Web Console now allow searching for messages with blank subject lines.
188548 Message digest sending is now more robust when network connectivity is poor.
188864 The Web Components configuration tool correctly sets the selected authentication setting.
189432 Images in PowerPoint files were not scanned in some 6.0 versions. Fixed.
190831 The Configurator now correctly handles importation of TLS certificates requiring passwords.
191358 The POP3 service now respects the configuration setting to exclude logging socket errors to the Windows logs.
191368 LDAP connections now have a configurable LDAP version setting.
193789 Two Classification Summary reports have been updated to reflect database changes. The Email Traffic Summary by Selected User report now loads correctly.
194027 Behavior of the Rule Condition Category Types interface has been corrected.
195973 Spam Console now successfully processes logins for users in OUs with names including '&'.
196406 Upgrading from version 6.0 now preserves the MIMA license if installed.
197195 Using TLS caused multiple Windows sockets errors. Fixed.
197589 Using TLS caused remote node Controller services to fail. Fixed.
197594 The Array Manager can run a custom script when committing changes. 
197641 The upgraded product license key is correctly saved after installation.
197642 Database upgrade from 6.0 to 6.1 could fail silently. Fixed.
198530 Console search with 'message history' unselected caused an error. Fixed.
198531 Marshal branding has been applied to all interfaces and documents.
198550 Installation now correctly creates the database on SQL Server 2005
198556 With TLS, the receiver did not properly issue a 221 after receiving a QUIT. Fixed.
198557 MailMarshal Sender now uses SSLv23 for TLS by default. TLSv1 can also be configured.
198560 A memory leakage issue while using TLS has been corrected.
198562 In the New User Group Wizard, ampersand characters were not correctly displayed. Fixed.
198582 Version information was not correctly updated in Registry upon installation. Fixed.
198588 Build version numbers for the Reports match the main product versions.
198592 Active content pages in the Configurator no longer raise an ActiveX security warning.
198593 The installation Autorun has been updated to improve functionality.
198595 Default SpamCensor scripts have been updated.
198596 The rule action 'Goto next ruleset' now correctly passes to the next policy group if required.
198598 The Web delivery package has been simplified to avoid confusion when upgrading.
198599 SQL 2005 Express is correctly detected by the installer.
198604 Installer screens show the currently supported SQL Server versions.
198607 Changing Digest templates from HTML to Text could cause format errors. Fixed.
198610 Upgrading from version 6.0 may take some time for SQL upgrade. An information box was added.
198615 The MSDE installer now notes that system restart may be required.
198618 Installation path can be selected when installing Array Manager only.

Copyright © Marshal Limited 2007