Event Id | 660 |
Source | MSExchangeMTA |
Description | The queue backlog for /O=MICROSOFT/OU=GUITARS /CN=CONFIGURATION/CN=CONNECTIONS/CN=X400 CONNECTOR TO BRASS_KITTEN has subsided leaving 250 messages in the queue. [MTA GATEWAY 45 512] (14) |
Event Information | According to Microsoft: The work queue alarm can be configured by using only the "Work queue alarm on" registry value. When the "Work queue alarm off" registry value is not present, the MTA will automatically substitute half the value specified in the "Work queue alarm on" registry value for the "off" value, which uses the 667 event to be triggered. The example events shown above illustrate this configuration, where the "Work queue alarm off" value is not present in the registry and the "Work queue alarm on" registry value has been set to 600 decimal. The "Work queue alarm off" registry value can be configured to log the 667 event at a different value if the administrator wants. For example, if the "Work queue alarm off" registry value is set to a value of 0, the 667 event will not be logged until the work queue has been emptied completely. Another example would be to set the "Work queue alarm off" value to 100 decimal, which would result in the 667 event being logged when the work queue diminishes to 100 messages. If the "Work queue alarm off" value is set to a higher value than the "Work queue alarm on" value, the value specified for "Work queue alarm off" will be ignored, and the default value of half the "Work queue alarm on" value will be used instead. The "Outbound queue alarm on" and "Outbound queue alarm off" registry values work similarly to the work queue alarm settings. The outbound queue alarm works independently from the work queue alarm. The outbound queue alarm logs a 659 event ID when a queue reaches the specified limit. |
Reference Links | XCON: MTA Logs Warning Events When Queues Reach Specified Sizes |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.