XCON: Read Receipt May Not Be Returned From ISOCOR MTA

 Last reviewed: January 30, 1998
Article ID: Q170054
The information in this article applies to:
  • Microsoft Exchange Server versions 4.0, 5.0, and 5.5

SYMPTOMS

When a Microsoft Exchange user sends a message with a read receipt request to an ISOCOR message transfer agent (MTA) user, the ISOCOR MTA may not send back a read notification report.

CAUSE

This behavior can occur when the Microsoft Exchange user sends the message to an ISOCOR user with the following X.400 address: 

   C=us;A­md;P=prmd;O=organization;S=surname;CN=common-name
When the CN address field is used over a 1984 mode X.400 connection, it is moved to the Domain Defined Attribute (DDA) field during the downgrade process. If the message also contains a delivery receipt request, the ISOCOR MTA sends that, but does not send back a read notification report. This has been found to be a limitation in the ISOCOR ISOPLEX 800 v.1.15. This behavior is by product design. 
Keywords          : XCON
Component         : MTA
Version           : WinNT:4.0,5.0,5.5
Platform          : winnt
Issue type        : kbbug

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: January 30, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.