XFOR: Message Loop Across Two Mail Systems

• Microsoft Exchange Server versions 4.0 and 5.0

SYMPTOMS

A Microsoft Exchange Server distribution list (DL) may contain recipients that exist on both sides of a connector (for example, on a TAO host and in Exchange Server). If dirsync is enabled and propagation of DLs is allowed, the Exchange Server DL will show up in the foreign mail system, usually as an individual recipient within the foreign mail system. If a user on the foreign mail system sends a message to that DL, the DL will traverse the connector and be fanned out at the DL's creation point (in this case Exchange Server).

Once DL expansion is completed, Exchange Server attempts to send to all recipients. If one or more of these recipients reside on the foreign mail system, then when Exchange Server attempts to send to these recipients, the connector will recognize that the correlation ID of this message is the same as that of the original message (original DL). The connector will detect this as a looping message and a corresponding log entry will be written. This is because each message that traverses the connector has a unique correlation ID. During message conversion this ID is extracted and appended to the correlation table. If two instances of a message traverse the connector with the same correlation ID, the connector will attribute this to a looping message.

RESOLUTION

To resolve this problem:

• In order to modify the default behavior of message-looping detection, add the following parameter to the [LME] section of the Linkage.ini file:

        DISABLETRACECHECKEX = YES
  

MORE INFORMATION

This behavior is by product design.

Keywords          : XFOR kbtshoot kbusage
Version           : WinNT:4.0,5.0
Platform          : winnt