This article applies to:
- Trustwave MailMarshal (SEG) 10.0
Question:
- What are the Release Notes for Trustwave MailMarshal (SEG) 10.0?
Information:
Trustwave SEG version 10.0.7 (10.0.7.3979) was released on September 29, 2023.
The Release Notes included with the product are generally accurate as of the date of publication.
This article provides any additional information or corrections generated after that date.
- Note that the earlier release 10.0.7.3969 was withdrawn due to an issue identified with TLS compatibility. Any customers who installed this earlier release should upgrade immediately.
- A small number of installations may use customized TLS cipher lists. These lists will require update. See article Q21203.
See also Current Known Issues.
Knowledgebase articles have been reviewed and updated as necessary to reflect changes in MailMarshal (SEG) 10.
Important Fixed Issue:
- 10.0.4 Folder changes cause quarantine problem: If you edit properties of a Folder in version 10.0.4, the physical path location information is lost. Message files are stored in an incorrect location. Message details and release for earlier quarantined messages do not work.
- This issue is corrected in later versions. However, any changes made in 10.0.4 are not automatically fixed.
- For customers who encounter this issue, a tool is available to detect incorrectly configured folders and move the incorrectly stored files. Contact Trustwave support.
Prerequisites:
MailMarshal (SEG) 10.X installs and requires .NET Core Hosting Bundle (for 10.0.7, the version installed is 6.0.20).
MailMarshal (SEG) 10.0.5 and below enforces a requirement of .NET Framework 3.5 SP1 (used by the Support Tool).
- 10.0.6 and above removes this dependency because the latest Support Tool does not require .NET 3.5
- For help with installing .NET on Server 2016 or above, see Trustwave Knowledgebase article Q21136.
MailMarshal (SEG) 10.X requires that WebDAV not be installed on the Array Manager server.
MailMarshal (SEG) 10.X requires IIS with the Windows Authentication feature on the Array Manager server.
Upgrade Issues:
- Installer exit after checking Visual Studio Run-times: On some systems the installer will exit with no warning after checking for Visual Studio updates.
- Run the installer again to continue.
- Commit Scheduling/Manual commit required: If Commit Scheduling is active, and you perform the upgrade outside the scheduled commit times, after upgrading all servers you must manually commit configuration to ensure all processing nodes receive the upgraded configuration.
- Website creation: In rare cases the upgrade may report issues with creation of the SEG Configuration Website, SEG Configuration Database or login credentials.
- These issues can be repaired - contact Support for assistance.
- If McAfee Endpoint Security is active, creation of the Configuration Website may be blocked by the "Windows EFS Abuse" rule. Disable this rule or create appropriate exclusions.
Management Updates:
MailMarshal (SEG) 10 introduces changes in the way the software is managed day-to-day. In particular note the following items:
User Interfaces
For MailMarshal (SEG) 10, all items previously found in the Console and Configurator are now accessed through the web Management Console. The separate Web Console application no longer exists. The main menu tree of the Management Console includes most of the familiar headings from both Configurator and Console.
- Array configuration items (Server and Array Configuration and Trustwave SEG Properties) are located in the System Configuration section.
- Properties and status for individual servers (nodes) are located in the Mail Servers section. This section also includes the mail queue information formerly located in the Console.
Registry references
In MailMarshal (SEG) 10, Array Manager Registry entries within sub-key "Default" are replaced by the Advanced Settings page of the Management Console. See Help for the Management Console.
- For example the registry entry
HKEY_LOCAL_MACHINE\SOFTWARE\Trustwave\Secure Email Gateway\Default\Engine\LogSpamAlways
becomes an Advanced Setting named Engine.LogSpamAlways
Array Manager and Node entries are generally found in JSON files.
For more details, see article Q10832.