XADM: Extra Read Receipt May Be Sent from Delegate (284954)



The information in this article applies to:

  • Microsoft Exchange Server 5.5

This article was previously published under Q284954

SYMPTOMS

When you send mail with a request for a read receipt to a recipient who has an autoforward rule set up for a delegate, if the mail recipient and the delegate are on different servers, an additional read receipt is generated from the delegate to the mail recipient. You receive a read receipt from the mail recipient when the mail item is read, as expected. No additional read receipt is received if the recipient and delegate are on the same server.

CAUSE

This problem occurs because when the delegate opens the mail message, the check that is made to determine whether to generate a read receipt does not verify whether or not the message was autoforwarded.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Exchange Server 5.5 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:

Component: Information store

File nameVersion
Store.exe5.5.2654.54

NOTE: Because of file dependencies, this fix requires Microsoft Exchange Server version 5.5 Service Pack 4.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5.

Modification Type:MinorLast Reviewed:10/6/2005
Keywords:kbHotfixServer kbQFE kbbug kbExchange550preSP5fix kbfix kbQFE KB284954