Microsoft KB Archive/166554

{| = XCON: Delivery and Read Reports Show OU2 and OU3 Values =
 * width="100%"|

Last reviewed: January 28, 1998

Article ID: Q166554 The information in this article applies to:


 * Microsoft Exchange Server, versions 4.0 and 5.0

SYMPTOMS
When you send a message to an X.400 recipient with a Read or Delivery Notification request, you may receive a report that looks like the following:

Your message To:X400 User Subject:This is a test Sent:6/27/97 3:03:17 PM

was delivered to the following recipient(s): c=US;a= ;p=Orgname;o=Sitename;s=User;g=X400;ou2=TEST;ou3=user.test; on  6/27/97 3:04:28 PM   MSEXCH:MSExchangeMTA:Sitename:servername

CAUSE
Microsoft Exchange Server incorrectly handles a report coming back from a 1984-mode X.400 system. When the Exchange Server message transfer agent (MTA) receives the report, it looks for a Content.Tag to determine the content of the report. Because 1984 mode does not support the use of content tags, the MTA simply uses the O/R address and sends it to the information store (IS). The IS then incorrectly switches any DDA type and value fields to OU2 and OU3.

WORKAROUND
To work around this problem:


 * If possible, use 1988 mode X.400 for communication between Exchange Server and a foreign system. This problem will not occur because 1988 mode supports the use of content tags.

STATUS
Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 4.0.

A supported fix is now available, but has not been fully regression- tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0. A supported fix is now available, but has not been fully regression- tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.
 * }