XCLN: REPLY ALL: Inserts Sender's Address

Last reviewed: April 3, 1997
Article ID: Q141982
The information in this article applies to:
  • Microsoft Exchange Windows 95 client, versions 4.0 and 5.0
  • Microsoft Exchange Windows 3.x client, versions 4.0 and 5.0
  • Microsoft Exchange Windows NT client, versions 4.0 and 5.0
  • Microsoft Exchange MS-DOS client, versions 4.0 and 5.0

SYMPTOMS

When you click Reply All to a message stored in your Sent Folder on a Microsoft Exchange, version 4.0, client, the sender's name is included in the Address list.

CAUSE

This is by product design.

MORE INFORMATION

Messages that you receive from other people have your identity stamped on them by the transport. On a reply or reply all, the Exchange client always puts the sender's name in the address list, then uses your identity as found in the original message to strip your name from the address list. Messages in your Sent Items folder do not have your identity because they are dropped in the folder by the spooler and do not pass through the transport. Therefore, the sender's name (yours) is not removed on a reply-all message.

Steps to Reproduce:

  1. Compose a message to someone other than yourself and send it.
2. Go into the Sent Mail folder and Reply All to the message just
   sent.

The sent message will contain the address of the sender.


Additional query words: reply all compose
Keywords : kbusage XCLN
Version : 4.0 5.0
Platform : WINDOWS


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: April 3, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.