How do I import or export email addresses or domain names into a User Group in MailMarshal?

This article applies to:

• Trustwave MailMarshal (SEG)
• Trustwave ECM/MailMarshal Exchange

Question:

• How do I import or export email addresses or domain names into a User Group in SEG?
• How do I import users from an external file?
• Where does SEG store User Group information?

Procedure:

Please also refer to the following articles.

• Q11305 How do I manually input email addresses into a User Group folder
• Q11401 How to manually create an Allow List and use it within a rule

Import

SEG/MailMarshal stores all User Group information in the SQL database. To import users from an external file, you can run the external utility GroupFileImport.exe found in the SEG install location. For detailed information and instructions, see the User Guide for the specific product version. You can find the User Guide on the SEG or MailMarshal Exchange documentation page (login required).

With SEG 8.0 and above, you can also import a group through the SEG REST API. See article Q20867.

You can also use Directory Connectors to synchronize from AD or LDAP.

Export

With MailMarshal (SEG) 10.X, currently the only way to export a group is through the SEG REST API. See article Q20867.

With SEG 8.X and below, to export a single User Group you could use the MMC "Export List" functionality.

1. In the Configurator, navigate to the User Group you want to export.
2. Click Action > Export List. You can select CSV or tab separated text output.
3. To extract a single column from the output file, use Excel or other spreadsheet software.

Notes:

The SEG/MailMarshal files could be found in a different location. MailMarshal may have been installed in a user-selected location, and earlier versions of MailMarshal were installed by default in different locations.

For more information on default installation locations for SEG/MailMarshal SMTP, see the following Knowledge Base article: 

• Q10832 - MailMarshal SMTP Install Paths and Registry Key Locations

This article was previously published as:

NETIQKB36462