Adjusting notification time for Receiver idle alert


This article applies to:

  • Trustwave MailMarshal (SEG)

Question:

  • How can I adjust the time before Receiver idle notification is sent to the Windows Event Log?

Information:

MailMarshal logs an event in the Windows event log if no connections are made to the Receiver for a long time.

By default the event is logged if no connections are made for 180 minutes (3 hours).

An example event appears as below:

 

Event Type: Error
Event Source: MMReceiver
EventCategory:None
EventID:2507
Date:7/19/2013
Time:1:46:02 AM
User:N/A
Computer: XXXXXXXX
Description:
Receiver idle alert raised. Alert 1 triggered: 
Receiver has not received any connection since 7/18/2013 10:45:22 PM

Procedure:

You can change the Receiver idle time by making an entry in the Registry.

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 solved. Make sure that you backup your Registry prior to making any changes.

  1. On the Array Manager, edit the Registry (10.X: use Advanced Settings in the Management Console)
  2. Navigate to the SEG Receiver key:
    • In version 8.X: HKEY_LOCAL_MACHINE\SOFTWARE\Trustwave\Secure Email Gateway\Default\Receiver
    • 10.X: value names have the prefix Receiver. (Receiver dot).
    • For full details of the location for each product version, see article Q10832.
  3. If the ServiceIdleTimeOut registry entry exists, edit the Value (as seen below).
  4. If this entry does not exist, add the value as follows:

    Data Type: DWORD (Integer)
    Value Name:  ServiceIdleTimeOut
    Value: Desired time in minutes. The default if the entry does not exist is 180 (Decimal).

  5. Commit Configuration Changes to update to the node(s).
  6. Restart the MMReceiver service on each node to complete the update. 

Last Modified 4/1/2020.
https://support.trustwave.com/kb/KnowledgebaseArticle16090.aspx