Trustwave SpiderLabs Exposes Unique Cybersecurity Threats in the Public Sector. Learn More

Trustwave SpiderLabs Exposes Unique Cybersecurity Threats in the Public Sector. Learn More

Services
Capture
Managed Detection & Response

Eliminate active threats with 24/7 threat detection, investigation, and response.

twi-managed-portal-color
Co-Managed SOC (SIEM)

Maximize your SIEM investment, stop alert fatigue, and enhance your team with hybrid security operations support.

twi-briefcase-color-svg
Advisory & Diagnostics

Advance your cybersecurity program and get expert guidance where you need it most.

tw-laptop-data
Penetration Testing

Test your physical locations and IT infrastructure to shore up weaknesses before exploitation.

twi-database-color-svg
Database Security

Prevent unauthorized access and exceed compliance requirements.

twi-email-color-svg
Email Security

Stop email threats others miss and secure your organization against the #1 ransomware attack vector.

tw-officer
Digital Forensics & Incident Response

Prepare for the inevitable with 24/7 global breach response in-region and available on-site.

tw-network
Firewall & Technology Management

Mitigate risk of a cyberattack with 24/7 incident and health monitoring and the latest threat intelligence.

Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Microsoft Exchange Server Attacks
Stay protected against emerging threats
Rapidly Secure New Environments
Security for rapid response situations
Securing the Cloud
Safely navigate and stay protected
Securing the IoT Landscape
Test, monitor and secure network objects
Why Trustwave
About Us
Awards and Accolades
Trustwave SpiderLabs Team
Trustwave Fusion Security Operations Platform
Trustwave Security Colony
Partners
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Trustwave PartnerOne Program
Join forces with Trustwave to protect against the most advance cybersecurity threats
Loading...
Loading...

HOWTO: Resetting the authentication mode for the Spam Quarantine Management Web site

Expand / Collapse


This article applies to:

  • Trustwave MailMarshal (SEG)
  • Trustwave ECM/MailMarshal Exchange 7.X

Question:

  • How do I reset the authentication mode for the SEG/MailMarshal SMTP Spam Quarantine Management (SQM) website?
  • How do I reset the authentication mode for the ECM/MailMarshal Exchange Quarantine Management (QM) website?

Procedure:

Warning: Using the Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Trustwave cannot guarantee that problems resulting from the incorrect use of Registry Editor can be resolved. Make sure that you back up your Registry prior to making any changes.

You can only set the authentication mode for the Spam Quarantine Management Web site once.  This restriction is intended to ensure consistency if you use more than one Web server to host this site. If you have selected the incorrect authentication mode and wish to change it, you can delete the authentication information. Users will lose all logins, delegation settings, and personal blocked and safe lists.

Note: The procedure differs by product and version. Be sure to follow the correct sections below.

Database Changes:

  1. Close all product user interfaces and stop the SQM or QM Web site on all servers where it is installed.
  2. On the Array Manager server, stop the MMArrayManager or MEXArrayManager service.
  3. On the SQL database server, connect to the SEG/MailMarshal SMTP or ECM/MailMarshal Exchange database
  4. Delete the data from the tables that contain SQM or QM user data. The tables are:
    UserList
    UserDelegate
    UserAlias
    [User]

    (Note that you must use brackets when entering the table name "User".)
     
    • Warning: Do not delete (drop or remove) the tables, but only the data.
    • Trustwave recommends that you use the SQL Server Management Studio tool to enter the query that performs these actions, as shown in the screenshot below. The "rows affected" will change depending on the user registrations on your system.
    • You can also use the command line SQL tool (OSQL). For details of the OSQL commands, see the notes at the end of this article.
       

       
  5. On the Array Manger server, run Regedit.
  6. Navigate to the MailMarshal Manager key
    • For Trustwave SEG 8.X and MailMarshal (SEG) 10.X the location is:
      HKEY_LOCAL_MACHINE\SOFTWARE\Trustwave\Secure Email Gateway\Manager
    • Note that in this particular case only, the Registry is the correct location to use for MailMarshal (SEG) 10.X.
    • For details of the locations for each SEG or ECM version, see the following Trustwave Knowledgebase articles:
      • Q10832 (SEG/MailMarshal SMTP)
      • Q14003 (ECM/MailMarshal Exchange)
  7. Within the Manager registry key, delete the value SSMAuthMode
  8. Start the MMArrayManager or MEXArrayManager service.

Website configuration

SEG/MailMarshal SMTP version 6.4 and above; ECM/MailMarshal Exchange 7.X

Note: When changing the settings, you must perform these steps on each web server. (However, a new server will retrieve the default settings from the Array Manager.)

  1. On a server hosting the web components, open IIS Manager.
  2. Navigate to the properties of the SQM virtual directory
    • For SEG/MailMarshal SMTP, by default this is Default Web Site/SpamConsole
    • For ECM/MailMarshal Exchange, by default this is MailMarshal Exchange Web Components/Quarantine Console
  3. If you are using IIS 6, select the ASP.NET tab and click Edit Configuration.
  4. On the General tab, in the Application settings section, locate the key InitialConfigurationComplete. Change the Value to False.
  5. On the Authentication tab, in the Authentication Settings section, verify that authentication mode Windows is enabled.
    • Note: This step is required to reset the mode. You will be able to select the desired authentication mode on the Configuration page of the site.
  6. Apply the changes and exit from IIS Manager.
  7. Using a web browser, open the default page of the SQM site. You should be directed to the Configuration page. Complete and save the settings including the authentication mode.
  8. Repeat these steps for each additional web server. Ensure that you use the same settings on each server.
     

MailMarshal SMTP versions below 6.4

Note: You only need to perform these steps once, even if your MailMarshal installation uses more than one web server.

  1. On a server hosting the MailMarshal Web components, run the MailMarshal SMTP Web Configuration Tool found in the MailMarshal program folder.
  2. Re-enter the Server name. This step forces the tool to update the configuration file on exit.
  3. Set the desired authentication mode and click OK.
  4. Restart the Spam Quarantine Management Web site on all servers. 
  5. In some cases, you may need to stop and restart the IIS services (you could run the Microsoft IISReset command if you have multiple IIS servers) on all Web servers to ensure that the DLLs associated with the Web site are reloaded.

Notes:

Using OSQL to clear the database tables
  1. On the server hosting the SEG/MailMarshal SQL database, open a command prompt. 
  2. Change to the directory containing the SQL executables (usually C:\Program Files\Microsoft SQL Server).
  3. Enter:
    osql -S <servername\instancename> -d <database> –U <username>
    where <servername\instancename> is the name of the server and SQL instance, <database> is the name of your SEG/MailMarshal SMTP or MailMarshal Exchange database, and <username> is the SQL username you use to connect to the database with MailMarshal.
    • For example: osql -S VM-EXAMPLE40\SQLEXPRESS -d MailMarshal –U sa
    • Default database names for SEG vary depending on product version. For details see Q10832.
  4. At the Password: prompt, enter the password associated with the user name you entered.
  5. At the numbered osql prompts, enter the following lines (You must type the square brackets in line 4):
    1> delete UserList
    2> delete UserDelegate
    3> delete UserAlias
    4> delete [User]
    5> go

    The result should be:

    (n rows affected)
    (n rows affected)
    (n rows affected)
    (n rows affected)
  6. Then enter:

    1> quit

This article was previously published as:
NETIQKB40664

To contact Trustwave about this article or to request support:


Rate this Article:
     
Tags:

Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster
.