XFOR: When Remote Clients Support MAPI, BP9 not SentLast reviewed: February 12, 1998Article ID: Q169685 |
The information in this article applies to:
SYMPTOMSForwarding messages by way of an X.400 connector may result in messages without a message body part arriving at foreign (non-Exchange) X.400 systems. This represents a loss of data in these foreign systems.
CAUSEWhen you select the "Remote clients support MAPI" check box on the X.400 Connector general property page, this causes the Microsoft Exchange message transfer agent (MTA) to drop the X.400 protocol for forwarded messages. As a result, non-Exchange systems may see messages that do not have a message body part.
WORKAROUNDTo work around this problem:
STATUSMicrosoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 5.0. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K MORE INFORMATIONEven though the Microsoft Exchange MTA behaves as it has been configured, Microsoft recognizes the need to be able to send the X.400 protocol along with the message. The need for the required behavior discussed in this article should become more distinct by looking at the scenario outlined below. Microsoft Exchange Server acts as a common backbone for both Microsoft Exchange Server systems and non-Exchange X.400 systems. At Exchange systems off the backbone, administrative burden can be eased, by using a minimal configuration to connect to the Exchange X.400 backbone. This minimal configuration could for example include an address space of 'C=*' on the X.400 connector to the backbone. On the same connector, the 'Remote clients support MAPI' check box is activated, for maximal Exchange interoperability. Without the hotfix discussed here, the X.400 protocol for forwarded messages would be dropped for messages sent over such an X.400 connector. On forwarding such a message from the Exchange backbone to a non-Exchange system, data loss will occur, because the message will not have a message body part. The X.400 protocol for forwarded messages is sometimes referred to as BP9. Please note that the MS Exchange MTA behaves as described in this article, because it is configured that way. The fix discussed herein allows to configure the wanted behavior on a per connector basis. The default behavior for Exchange is to drop BP9 on X.400 links configured with the option 'Remote clients support MAPI'. Please do the following to allow BP9 being sent additionally, after applying the hotfix, for EACH X.400 connector you want Exchange's default setting to be changed:
INSTALLATION
Keywords : kbbug5.00 kbfix5.00.sp2 XFOR kbusage Version : WinNT:5.0 Platform : winnt Issue type : kbbug Solution Type : kbfix |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |