MailMarshal SMTP

Version: 6.4.6, Last Revision: August 04, 2008

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 Q11909.

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.4.5

Enhanced Dead Letter Templates: Separate Dead Letter templates are available for incoming and outgoing messages.
Secure Email Server integration: MailMarshal SMTP can now integrate seamlessly with MailMarshal Secure Email Server for S/MIME encryption and signing. To learn more, see MailMarshal Secure Email Server documentation.

Features New in 6.4

Enhanced Routing: Routing tables with multiple load balancing, fallback hosts, and special cases can be created. Local delivery can be set by server name.
Enhanced Anti-Relaying: Multiple Anti-Relaying tables can be created and selected separately for each node in an array.
Updated Spam Quarantine Management website: The site has been redeveloped in ASP.NET 2.0. The Administrator has GUI access to view and change user whitelists, blacklists, and additional addresses. Skins and language packs are supported.
Marshal Notifications: The Console provides a RSS based alert and news service.
SpamProfiler: A new layer of Spam filtering that allows denial of spam messages at the Receiver.
Automatic Adaptive Whitelisting: Allows Reputation checks (DNS Blacklists) to be skipped for trusted servers.
Enhanced SpamCensor: SpamCensor can now base action on attachment contents.
7zip files support: Unpacking of 7zip files files is supported.
Enhanced low disk space handling: includes a warning and stop threshold, with periodic email notifications
Event Log viewer: Console provides a view of event logs on all servers in the MailMarshal installation.
Centralized Upgrades: Upgrades can be delivered to all servers in an array using the Configurator interface (after the initial 6.4 upgrade has been applied to all servers).
Sophos for Marshal is supported by trial keys.

Features New in 6.3

Appliance Release Only: MailMarshal 6.3 provides support for the MailMarshal Node Appliance.

Note: Version 6.3 cannot be installed with software email processing servers.

Appliance Release Features:
- Email Processing Servers are hardware appliances
- Array Manager and user interfaces are software applications.
- McAfee for Marshal virus scanner included
- Additional user interface changes to allow remote management of Appliance nodes
- Enhanced low disk space handling with periodic email notifications. See Marshal Knowledge Base article Q11669.
Event Log viewer: Console provides a view of event logs on all servers in the MailMarshal installation.

Features New in 6.2

SPF Support: Sender Policy Framework is now implemented as a Receiver Rule condition.
Sender ID Support: Sender ID is now implemented as a Standard Rule condition.

Features New in 6.1.8

Additional Message Digest options: New Message Digest templates are available, including a template with one line per message. Digests can now cover multiple folders and can be limited to members of specific user groups. Multiple digest schedules can be created.
Improved Directory Harvest Attack protection configuration: DHA protection now allows selection of one or more groups to query for the list of valid local users.
Local Domains: Change in Local Domains no longer requires service restart.
Load Balancing: Load Balancing of delivery is now available for outbound delivery (MX round robin and alternate forwarding hosts) and local domain delivery.

Features New in 6.1.6

Image Analyzer (scanning and classifying of images as potentially pornographic content). Image analysis is implemented as a new rule condition. The Image Analyzer software is included in the MailMarshal installation and trial license. Full licensing is available through Marshal.
PestPatrol for Marshal malicious content scanning is implemented as a DLL based scanner (available through Virus Scanning rule conditions). A separate installation is required for the configuration console. MailMarshal trial licenses include support for this scanner. Full licensing is available through Marshal.
CounterSpy for Marshal malicious content scanning is implemented as a DLL based scanner (available through Virus Scanning rule conditions). A separate installation is required for the configuration console. MailMarshal trial licenses include support for this scanner. Full licensing is available through Marshal.

Notes:

Windows 2000 installations of this release may require a server restart due to installation of updated prerequisites. See Notes on Upgrading.

Matching of external command results using ranges (such as 1-5) has been changed in this release. This feature now performs as previously documented. See the Change History entry for MM-96. If you use external commands with result ranges you should review the external command definitions.

Features New in MailMarshal SMTP 2006 (6.1.4)

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

Zero-Day attack protection
Denial of Service (DOS) gateway protection
Directory Harvesting Attack (DHA) gateway protection
Transport Layer Security (TLS) encryption support
Spam categorization and reporting
CountryCensor – anti-spam by country of origin
URLCensor – anti-spam / anti-phishing using real-time URL lookups
Support for Norman Anti-Virus ‘sandbox’ functionality
HELO support for MailMarshal ESMTP Receiver Policies
Additional reports, including new anti-spam categorization reports

Upgrading MailMarshal

MailMarshal SMTP version 6.X supports a direct upgrade from MailMarshal SMTP 5.5 and later versions.

Note: This release of MailMarshal 6.4 cannot be used to upgrade a MailMarshal 6.3 Appliance installation.

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:

Q11025 Upgrading from MailMarshal 5.5 to MailMarshal SMTP 6.X
Q11026 Upgrading from MailMarshal 6.0 to MailMarshal SMTP 6.X
Q11027 Upgrading from MailMarshal 6.1.3 to MailMarshal SMTP 6.X

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

Changes in Database Structure and Prerequisites

MailMarshal SMTP 6.X 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:

Microsoft SQL Server 2000 (Service Pack 3)
Microsoft SQL Server 2005
MSDE 2000 (Service Pack 3)
SQL 2005 Express

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 6.X

Upgrading a MailMarshal SMTP Secure Server

MailMarshal SMTP 6.X 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 Q11909.

6.4 Operating System Support: As of version 6.4, MailMarshal is no longer supported on Windows 2000. You cannot install MailMarshal 6.4 on Windows 2000. If your existing MailMarshal installation is on a computer running Windows 2000, you will not be able to upgrade.
6.4: SpamProfiler: Version 6.4 introduces the SpamProfiler service. This service allows MailMarshal to pre-filter spam at the Receiver. SpamProfiler is enabled by default on new installations. As part of the upgrade process you can choose to enable SpamProfiler (strongly recommended).
- SpamProfiler requires internet access from each processing server. To configure usage and proxy options, see the Spam and Internet Access tabs of Server and Array Properties. For additional information see the User Guide and Marshal Knowledge Base article Q11927.
6.4: Disk space requirements: Version 6.4 introduces significantly higher default requirements for free disk space (1GB free space preferred). On upgrade of a single server installation, you will be warned if less than 1.5GB of free space remains. In an array installation, you should check free space on each server manually. For more details on the disk space settings, see Marshal Knowledge Base article Q11669.
6.4: POP3 aliases: Version 6.4 and above does not support POP3 aliases for domains that are outside your local domains list. If you have previously defined such aliases, after you upgrade email will no longer be delivered to them.
During the upgrade from version 6.1.8, the MailMarshal Controller may stop with an error. In most cases the Controller will restart automatically. This behavior is related to issue MM-429, first fixed in version 6.2.0.
6.2: McAfee for Marshal Update: If you are using McAfee DLL based scanning, you must upgrade from Marshal Integrated McAfee (MIMA) 4.4 to McAfee for Marshal 5.100 before upgrading to MailMarshal 6.2. The MailMarshal Engine will not process email using the McAfee 4.4 engine. McAfee terminated support for version 4.4 in January 2007.
In version 6.2, the internet access proxy setting 'Preset' option is no longer available. During upgrade the 'Preset' option will be changed to 'Direct Access'.
6.1.6: MDAC Prerequisite: MailMarshal requires a minimum of MDAC 2.7. Some Windows 2000 systems will require an upgrade to MDAC. MDAC upgrades normally require a server restart. If this upgrade is required, installation will stop so you can install MDAC. The MailMarshal CD includes MDAC 2.8. The web version of the setup autorun provides a download link from the Prerequisites tab.
6.1.6: For External Commands, if you have configured a range of return values, the interpretation of the range entry has changed. See the Change History entry for MM-96.
When upgrading from MailMarshal SMTP 6.0 to MailMarshal SMTP 6.X, the database upgrade will require approximately 5 minutes per GB of data. You should schedule your upgrade with this time requirement in mind.
By default the MailMarshal SMTP 6.X installation places the Unpacking or Explode folder within the MailMarshal SMTP installation folder. If your Unpacking or Explode folder is configured in another location, you can select that location on the Choose Destination Location window of the installation wizard.
Message Release codes generated by MailMarshal SMTP 5.5 will not be accepted by the Message Release external command under MailMarshal SMTP 6.X.
MailMarshal SMTP 6.X automatically logs a classification record for each quarantine action such as "move message to folder." After upgrading, review the rules and eliminate duplicate classification actions.
For information about upgrading LDAP and Active Directory connectors, see the section about upgrading MailMarshal SMTP in the MailMarshal User Guide.
The upgrade installation does not install any new rules. After upgrading, you can import sample rules that support the new features available in the specific release. For more information, see Marshal Knowledge Base article Q10336.
If you intend to use the Quarantine Upgrade Tool to migrate data from a 5.5 database, the same username and password must be valid for access to both the old database and the new database. For information about changing the password for a MailMarshal SMTP database hosted on MSDE, see Marshal Knowledge Base article Q10763.

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:

Close all instances of the MailMarshal Configurator, MailMarshal Console, and MailMarshal Reports.
Use Add/Remove Programs from the Windows Control Panel to remove MailMarshal SMTP.
Use Add/Remove Programs from the Windows Control Panel to remove additional components you may have installed, such as Web components or Reports.
If you have installed any components (such as the Configurator, Console, Web components, or Reports) on other computers, uninstall them.
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 installation of the MailMarshal SMTP Array Manager and selected database.

Hardware and software for the Appliances (email processing nodes) is pre-configured.
A full discussion of requirements for all supported configurations is available in the MailMarshal SMTP User Guide.


Category	Requirements
Processor	Pentium 4
Disk Space	10GB (NTFS)
Memory	512MB
Supported Operating System	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 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
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.
Port Access	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 Port 19001 - between Array Manager and Appliances Note: Additional ports are required by the Appliances for email and updates.

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 Q11909.

6.4.6 (August 04, 2008)

MM-1896

In version 6.4.5, messages were not automatically released from parking folders as specified. Fixed.

6.4.5 (June 26, 2008)

MM-781	Receiver Rule logging could cause database deadlock errors. The issue has been further addressed with sorting of items from multiple nodes.
MM-1447	DeadLetter templates now include separate options for inbound or outbound messages.
MM-1486	A new more descriptive variable name `{ReputationServices}` duplicates `{MMSmtpMapsRBL}`.
MM-1487	DOS and DHA blocking times are now based on the time when the block was first applied (not the time of the most recent attempt).
MM-1488	Folders and classifications now cannot be deleted when they are used in classification groups.
MM-1493	Automatically generated trial keys now support Sophos for Marshal.
MM-1495	MailMarshal can now unpack Microsoft SZDD archives.
MM-1496	Certain upgrade scenarios could create an open email relay. Fixed.
MM-1503	The Route to Host rule action now accepts a port number.
MM-1507	SQM did not allow updating a safe or blocked entry to a wildcard string. Fixed.
MM-1510	The installer now checks for and installs the correct version of Microsoft Visual C redistributable (8.0 SP1)
MM-1511	SpamProfiler updating now supports NTLM for proxy authentication.
MM-1516	Receiver rule checking for FQDN hostnames now accepts hostnames with between 3 and 10 parts by default. This behavior can be changed with a Registry entry. See Marshal Knowledge Base article Q12041.
MM-1518	Messages quarantined by SpamProfiler and released could pass through MailMarshal without being virus scanned. Fixed with rule changes.
MM-1519	When the engine started, it could create a crash dump zip file unnecessarily. Fixed.
MM-1524	The Route to Host rule action can now specify that the remote host is MailMarshal SES. Additional data is sent to preserve message logging between servers.
MM-1551	The Standard Rule action "delete message" now includes an option to delete with no SQL logging.
MM-1552	The SpamCensor updater now provides a better error message when update fails due to problems retrieving the Certificate Revocation List.
MM-1556	Releasing a message from the SQM website did not honor the folder options for pass through or continue processing. Fixed.
MM-1559	Message purging speed has been addressed with SQL index hints. The PurgeMessagesFast stored procedure has been removed.
MM-1568	Image Analyzer has been updated to the latest available version.
MM-1576	The rule condition "Where Sender's IP address matches address" is now available in Standard rules as well as Receiver rules.
MM-1761	The `{Reputation Services}` and `{MMSMTPMapsRBL}` variables now correctly show the name of the service that triggered a rule.
MM-1765	Some other servers could reject MailMarshal digest messages as malformed due to invalid UTF-7 encoding. Addressed with a registry setting to disable this encoding if necessary.
MM-1788	Internet access settings for nodes were not honored. Fixed.
MM-1793	The LDAP connector now has improved ability to recognize the end of returned data ("no such object").
MM-1823	Some 2007 office documents could cause the engine to consume a large percentage of your CPU. Fixed.
MM-1830	The size of images Image Analyzer scanned were not being checked. Fixed.

6.4.1.5038 (March 06, 2008)

MM-1382	MP3 files could cause the file type checker to exit unexpectedly. Fixed.
MM-1396	Receiver disk check could give incorrect results. Addressed with updated logic. Also, this check can now be disabled. See Marshal Knowledge Base article Q11669.
MM-1398	Messages tagged by SpamProfiler could never be released when reprocessed. Fixed.
MM-1400	Creation of zip files used for debugging of the unpacking process could cause issues. Fixed.
MM-1406	SpamProfiler now allows exceptions by User Group and by Safe Senders lists.
MM-1412	In previous 6.4 releases, environment variables did not work in message templates. Fixed.
MM-1418	Inappropriate POP3 alias errors appeared in the event log when POP3 accounts were created for authentication. Fixed.
MM-1422	Upgrade converted anti-relay IP ranges (from netmask to range format) incorrectly. Fixed.
MM-1432	The Engine now supports "rule profiling" to record the average run time of a rule and the number of times it is run. The result can be queried using MMLookup.exe. See Marshal Knowledge Base article Q11981.
MM-1440	Problems with message formatting in the Sender service could cause the service to exit unexpectedly. Fixed.
MM-1442	The Sender notifications did not provide a detailed reason for failure. Fixed.
MM-1459	The -r (list of recipient fields) option of MMGetMail did not function. Fixed.
MM-1461	After upgrade some local domains variables in templates could be blank. Fixed.
MM-1467	Attempting to upgrade the Spam Quarantine Management component actually uninstalled it. Fixed.
MM-1475	The RemoteIP variable was not populated in the sender notification template. Fixed.

6.4.0.4772 (January 30, 2008)

MM-1337	Could receive error "Error talking to client 'nnn.nnn.nnn.nnn' Property IpAutoWhitelisted not found" when using TLS. Fixed.
MM-1363	The version number of the configuration merge file `CurrentConfigMerge.xml` was incorrect. Fixed.
MM-1367	Deleting messages for a route from the Console caused all later messages for that route to be deleted until the Sender service was restarted. Fixed.
MM-1373	Execution of a SQL query by the Array Manager to determine the license count has been removed for performance reasons.
MM-1374	Zero length strings could cause services to exit unexpectedly (due to change in behavior in a new version of runtime libraries). Fixed.

6.4.0.4743 (January 25, 2008)

MM-1355

The installer will now prevent installation on Windows 2000 machines (for both new installations and upgrades).

6.4.0.4714 (January 22, 2008)

MM-1333	When upgrading, the MMReceiver and BlockedHostIP tables could generate duplicates and cause the upgrade to fail. Fixed.
MM-1336	The Configurator ceased to function when the "Server and Array Properties" window has been opened from the "MailMarshal Manager properties" window. Fixed.
MM-1337	Could receive error "Error talking to client 'nnn.nnn.nnn.nnn' Property IpAutoWhitelisted not found" when RBL check is enabled. Fixed.
MM-1341	Certain regular expression behavior differed from previous releases. Fixed.
MM-1343	Option added to change SpamProfiler behavior to apply to inbound messages only, or inbound and outbound messages.

6.4.0.4659 (January 15, 2008)

MM-166	Routing overrides did not work for local domain delivery. Fixed.
MM-232	Message size is now available as a MailMarshal variable for use in templates. This variable reflects the size as originally received.
MM-345	Messages that cannot be delivered after multiple retries now have a final classification of "undeliverable."
MM-404	Deletion of nested user groups is handled properly.
MM-445	Messages in deleted folders no longer appear in the Console Mail Recycle Bin.
MM-447	Storage and reloading of "valid fingerprints" is now more efficient.
MM-449	Messages with no body are handled correctly at all points in the product.
MM-452	The Blocked Host IP table (used by DoS and DHA functions) is now purged of data over 7 days old.
MM-453	Forward slashes in Active Directory group member names could cause errors in updating the groups. Fixed.
MM-455	Some Unicode files were incorrectly recognized as Binary. Fixed.
MM-482	Server From and Administrator email addresses can now be set for each Local Domain and will be used for messages relating to the domain.
MM-492	Some subject lines were incorrectly converted from UTF-7 to Unicode. Fixed.
MM-516	Detection of MP3 files has been improved.
MM-550	The console now allows you to configure the oldest message to display in archive folders.
MM-568	The rule interface for Spam Type categories did not save the correct selection. Fixed.
MM-578	Certain attached log files could be identified as mail headers. Fixed.
MM-595	URLCensor did not correctly look up a URL ending in . (dot). Fixed.
MM-637	Image Analyzer behavior with unsupported TIF files is improved.
MM-640	SORBS Reputation Service is no longer used by default.
MM-669	The Sender can now be bound to a specific IP using a Registry entry
MM-738	The keyboard Delete key did not function correctly in the Console under MMC 3.0. Fixed.
MM-776	Deadlettered messages are now logged with folder classifications and can be reported on by folder.
MM-781	Receiver Rule logging could cause database deadlock errors. The issue has been further addressed with changes to batch insertion of these records.
MM-793	Error handling for SPF records over 512 characters was not correct. Fixed.
MM-818	Messages with MIME boundaries declared in the headers are now deadlettered by default.
MM-819	Active Directory imported groups that contain child groups could not be deleted. Fixed.
MM-821	Message count and size rule conditions now allow "equal to" and "not equal to" an exact value.
MM-891	Digest generation failed for email addresses with a comma in the local part. Fixed.
MM-906	If the MailMarshal Sender gets a 500 response to the DATA command, the message will be retried.
MM-922	Office 2007 files are correctly recognized and unpacked. See also MM-962.
MM-935	"Scraping" of email addresses from LDAP connectors has been improved and better documented.
MM-953	Mail Batching is no longer supported within the product. The `MMGetMail.exe` external utility is available to perform this function.
MM-962	Excel 2007 Binary format (.xlsb) files are recognized as "Excel 2007 Binary document" but not fully unpacked. See also MM-922.
MM-963	Rule criteria evaluation for "greater than 0" failed. Fixed.
MM-1001	Deadletter folders now have a default release type of pass through with no further processing.
MM-1039	A Category script has been added for HIPAA compliance support.
MM-1068	Sophos could be invoked twice for a message if used in multiple rules with different conditions. Fixed.
MM-1123	Regular Expression filtering is now available to limit the items written to text logs.
MM-1182	The MailMarshal Web Configuration Tool is not used by the 6.4 Web components and has been removed.
MM-1206	Message digesting could fail when using a classification, if a classification of the same name had previously been deleted. Fixed.

6.3.0.3361 (July 19, 2007)

MM-532	Low Disk Space handling has been enhanced to include a receiver slowdown threshold in addition to the receiver stop threshold.
MM-585	User Group information on the nodes is now stored encrypted.
MM-602	Receiver Rule logging could cause database deadlock errors. Issue has been addressed by batching the insertion of these records.
MM-621	Image Analyzer was failing on certain GIF files. Fixed.
MM-628	The Receiver no longer lists the version in response to SMTP request HELP VERSION. This is a security enhancement.
MM-644	DNS caching did not support round robin delivery. Fixed.
MM-647	Naming mail folders using digits only could cause errors. Fixed.
MM-651	Server Host Name field was not displayed after being updated in the Configurator. Fixed.
MM-652	Header Matching and Rewriting now works properly for fields up to 100 characters long.
MM-654	Image Analyzer now runs multi-threaded.
MM-656	MailMarshal now detects Office 2007 documents as PPTX, DOCX, and XLSX.
MM-668	MailMarshal dump files are now deleted automatically after a month (configurable).
MM-802	Zip files that use backslash as the path separator were deadlettered. Fixed.

6.2.2.3252 (September 07, 2007)

MM-911

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

6.2.1.3252 (June 25, 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 TLS/SSL 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. TLSv1 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.

To review Change History prior to version 6.2, please see the Release Notes for the specific versions.