Microsoft KB Archive/175040

From BetaArchive Wiki
Knowledge Base

XFOR: Read Receipts Not Translated Over AppleTalk Connector

Article ID: 175040

Article Last Modified on 11/1/2006


  • Microsoft Exchange Server 4.0 Standard Edition

This article was previously published under Q175040


When a Microsoft Mail for AppleTalk Networks sends a message to a Microsoft Exchange Server user and requests a read receipt, the AppleTalk connector returns a text message like this:

   To: AppleTalk User

   Microsoft Mail v3.0 IPM.Microsoft Mail.Read Receipt
   From: Exchange User
   Date sent: 1996-10-31 16:48
   To: AppleTalk User
   Subject:  Read Receipt: Exchange User
   Message Identifer: 8531445D0933D011B89B000000000001
   Primary message ID: 20D925BF0B33D011B89B000000000001
   Your message to: Exchange User(MS:MICROSOFT/BREST/EXUSER)
   With subject: Message Subject
   And sent on: 1996-10-31 11:06
   Was read on: 1996-10-31 16:48
   Priority level: C

Normally, AppleTalk read receipts are in the following graphical format:

   |          Message Subject                      |
   |   The message :  Subject     <stamp icon>     |
   |   was read by :      Receiver's Name          |
   |   on:       Thur. Oct 31, 1996 4:48pm         |


The AppleTalk connector does not translate Read and Not Read messages into graphical format.


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.


With the fix applied, read receipts are translated into graphical format. However, if the Exchange Server user deletes the message before it is read, then the notification will be in the form of a normal message with the prefix "Not Read" added to the subject. Even thought this is non-graphical, no header information will be included in the body of the message.

Keywords: kbbug kbfix kbqfe kbusage KB175040