Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/169299

From BetaArchive Wiki
Knowledge Base


Article ID: 169299

Article Last Modified on 10/28/2006



APPLIES TO

  • Microsoft Exchange Server 4.0 Standard Edition
  • Microsoft Exchange Server 5.0 Standard Edition
  • Microsoft Exchange Server 5.5 Standard Edition



This article was previously published under Q169299

SYMPTOMS

When you send a mail message to an HP Openmail message transfer agent (MTA) over an X.400 88 Connector in X.410 RTS mode (84), you may receive a non- delivery report (NDR) indicating that the originator of the message detected looping. Note that the recipient on the HP system does receive the message.

CAUSE

This behavior may happen if you select the default "Use the GDI from Site Addressing" option on the Advanced tab of an X.400 Connector and the remote MTA is in fact in a different Private Management Domain (PRMD).

RESOLUTION

To resolve this problem, specify a Global Domain Identifier (GDI) on the Exchange Server X.400 Connector that matches the remote system's GDI:

  1. In the Exchange Server Administrator program, select the X.400 Connector corresponding to the remote MTA:

    Org/Site/Configuration/Connections/<X.400 Connector>

  2. On the File menu, click Properties to edit the properties of this X.400 Connector.
  3. On to the Advanced tab, select the "Use the GDI specified below" option.
  4. Set the Country, ADMD, and PRMD values according to the remote site values.

The GDI, which is composed of three X.400 attributes (Country, Administration Management Domain, Private Management Domain), now contains the values of the remote site's attributes. This new setting will eliminate the loop detected NDRs.

MORE INFORMATION

When you select the "Use the GDI from Site Addressing" option in the advanced property page of an X.400 Connector, the Internal X.400 Trace Information is conveyed to remote MTA instead of being removed from P1 envelope. In some cases, for example if you have asked for a delivery receipt, this trace information causes a loop detection NDR to be sent back to Exchange user:

   Your message did not reach some or all of the intended recipients.

      Subject: Test message to HP Openmail
      Sent: 01.07.97 15:13:05

   The following recipient(s) could not be reached:

      /c=c/a=Admd/p=Prmd/o=Org/s=Surname/g=GivenName on 01.07.97 15:16:41
      The recipient was detected looping within the message transfer
     service.
                


Additional query words: Trace

Keywords: kbprb kbusage KB169299