Version: 5.8, Last Revision: June 15, 2017
These notes are additional to the Trustwave SES 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 Trustwave Knowledge Base article Q12026.
What's New
Installation Notes
Upgrading Trustwave SES
Uninstalling
Hardware and Software Requirements
Change History
See the Change History for additional minor features and bug fixes.
You can cleanly uninstall the program as follows:
d:\>osql -U sa Password: 1> drop database MailMarshalSESCertStore 2> go Deleting database file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\MailMarshalSESCertStore.mdf'. Deleting database file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\MailMarshalSESCertStore_log.LDF'. 1> exitSubstitute the name of your database. The file locations may differ. You may have two databases, one for Certificates and one for Logging/Reporting.
Hardware Required for Trustwave SES Server
Trustwave SES will run on any recent hardware designed for server installations. Hardware requirements naturally vary depending on the number of email users, the amount of email traffic, and other software that may be installed (such as Trustwave SEG or SQL with large reporting databases). The following minimum specifications are suggested as a guideline:
Sites with more than 10,000 users may require enhanced hardware. Trustwave SES supports multi-processor computers and various array implementations for very high traffic sites. Please contact Trustwave for a recommended configuration.
Note: Trustwave SES will not accept new messages if there is less than 100MB of free disk space available in the disk partitions where its working directories reside.
Trustwave SES server components require the following software
Trustwave SES Client Tools (Configurator and Console) can be installed on the following
Notes:
- The Trustwave SES installation will attempt to install some prerequisites if they are not present. Trustwave recommends that you install the pre-requisites prior to Trustwave SES installation so as to isolate any installation issues to the specific package.
5.8.1 (June 15, 2017)
MMS-269 | Header decryption for specific messages could cause the decrypt service to stop. Fixed. |
MMS-270 | Sender and recipient properties in the envelope were changed unnecessarily. Fixed. |
MMS-272 | The default setting for newly imported certificates is "strip digital signature". This is the recommended setting to avoid the messages appearing as malformed to email clients. |
MMS-274 | In some cases where an attachment was an Office 2003 document containing an embedded Office 2007/2010 document, the message was deadlettered due to an unpacking problem. Fixed. |
MMS-284 | Crash dumps could be empty in certain cases. Fixed. |
5.8.0.361 (May 19, 2016)
MMS-189 | The product is rebranded as Trustwave Secure Email Server. |
MMS-205 | Cryptographic Providers are now split into Storage and Algorithm Providers. |
MMS-238 | Use of Proxy Certificates is not supported in version 5.8. |
MMS-244 | CRL checking for certificates with more than one CDP is improved. |
5.7.2.9723 (May 1, 2013)
MMS-162 | In release 5.7.0, the SES-specific performance counters were not available. Fixed. To resolve issues with the counters after upgrade, see Q15044. |
MMS-164 | Upgrading caused logging to be disabled due to an issue reading database credentials. Fixed. |
MMS-165 | Importing an invalid configuration could leave the installation in an unusable state. Fixed. |
MMS-166 | The "Active Sessions Total" performance counter did not decrement when a connection was closed. Fixed. |
5.7.1.9707 (November 28, 2012)
MMS-159 | Additional Rule Conditions have been added for Secure Email Rules to allow detailed checking of certificate errors when encrypting, decrypting, or signing a message. |
MMS-160 | Connecting to a SES 5.6 installation with a 5.7 Configurator could leave configuration in an unusable state. Fixed: Connecting from a mismatched Configurator is no longer allowed. |
MMS-163 | The micalg header was not set correctly for messages signed with sha-2 algorithms. Fixed. |
5.7.0.9686 (September 3, 2012)
MMS-79 | The Encryptor was checking the database for expired CRLs every 10 seconds. Fixed: the recheck time is now 1 minute. |
MMS-100 | The Configurator encountered an error when attempting Copy/Paste actions on certificates from the Harvesting folder. Fixed: Only Cut and Paste is allowed. |
MMS-125 | In version 5.6, upgrading between minor versions failed. Fixed. |
MMS-127 | MailMarshal SES now supports AES-128, AES-192, and AES-256 encryption algorithms (when using Windows 2008 and Microsoft Enhanced RSA and AES Cryptographic Provider v2). |
MMS-129 | The Receiver service could incorrectly detect that the mailbox name was too long (more than 255 characters). Fixed. |
MMS-130 | MailMarshal SES now supports SHA-2 algorithms (SHA-256, SHA-384, and SHA-512). |
MMS-133 | The MMEncrypt service did not generate a notification when deadlettering a message. Fixed. |
MMS-138 | Version 5.7 supports upgrade or migration from version 5.6. |
5.6.0.5716 (August 8, 2010)
Copyright © 2017 Trustwave Holdings, Inc.
All rights reserved. This document is protected by copyright and any distribution, reproduction, copying, or decompilation is strictly prohibited without the prior written consent of Trustwave. No part of this document may be reproduced in any form or by any means without the prior written authorization of Trustwave. While every precaution has been taken in the preparation of this document, Trustwave assumes no responsibility for errors or omissions. This publication and features described herein are subject to change without notice.
While the authors have used their best efforts in preparing this document,
they make no representation or warranties with respect to the accuracy or
completeness of the contents of this document and specifically disclaim any
implied warranties of merchantability or fitness for a particular purpose. No
warranty may be created or extended by sales representatives or written sales
materials. The advice and strategies contained herein may not be suitable for
your situation. You should consult with a professional where appropriate.
Neither the author nor Trustwave shall be liable for any loss of profit or any
commercial damages, including but not limited to direct, indirect, special,
incidental, consequential, or other damages.
Trustwave and the Trustwave logo are trademarks of Trustwave. Such trademarks shall not be used, copied, or disseminated in any manner without the prior written permission of Trustwave.
Trustwave helps businesses fight cybercrime, protect data and reduce security risk. With cloud and managed security services, integrated technologies and a team of security experts, ethical hackers and researchers, Trustwave enables businesses to transform the way they manage their information security and compliance programs. More than three million businesses are enrolled in the Trustwave TrustKeeper® cloud platform, through which Trustwave delivers automated, efficient and cost-effective threat, vulnerability and compliance management. Trustwave is headquartered in Chicago, with customers in 96 countries. For more information about Trustwave, visit https://www.trustwave.com.