Article ID: 175499
Article Last Modified on 9/29/2003
APPLIES TO
- Microsoft Exchange Server 5.5 Standard Edition
This article was previously published under Q175499
SYMPTOMS
When you reply to a message sent from another Microsoft Exchange Organization or from another Site within the same Organization, you may immediately receive the following Non-Delivery Report (NDR) by the local Message Transfer Agent (MTA):
CAUSE
This behavior occurs when the two Microsoft Exchange Organizations are connected via the X.400 Connector, or when two Sites are connected via the X.400 Connector with the Address Space Tab configured, and have the Allow MSExchange Contents setting enabled.
When a computer running Microsoft Exchange Server sends a message to another Exchange Server computer, the P1 for that message contains only the X500 Distinguished Name (DN) for the recipient's address. When the recipient replies to the message, they reply to the DN of the message originator. However, in seperate Exchange Organizations, as well as two Sites configured with the Address Space Tab, this fails because the DN is only comprised of the Organization and Site names.
WORKAROUND
To work around this behavior, the administrator needs to go to the properties page for the X.400 connector that connects the two Exchange Organizations or Sites and do the following:
- Click the Advanced tab.
- Under X400 Link options, click to clear the Allow MSExchange Contents setting.
- Restart the MTA Service.
Now when messages are sent to the other Exchange Organization or Site, a content conversion occurs and the message P1 changes to a true X.400 O/R address that is properly handled by the other Exchange Organization or Site.
Additional query words: metamorf allow ms exchange content conv p22 rtf mapi 290
Keywords: kbbug KB175499
