Article ID: 317865 - View products that this article applies to.
This article was previously published under Q317865
When items uch as messages and meeting requests are sent by a delegate, on behalf of a manager, a copy of each item is saved in the delegate's Sent Items folder. This behavior is by design. This article describes how to save sent items to the manager's Sent Items folder instead of the delegate's Sent Items folder.
For Outlook 2003 a hotfix was developed to implement this functionality with limited changes required on the manager and delegate machines. For more information about the hotfix , click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/953804/ )An e-mail message does not appear in a user's mailbox if the e-mail message was sent on behalf of the user by a delegate in Outlook 2003
To save sent items to the manager's Sent Items folder and not the delegate's Sent Items folder, the delegate must be logged on as the manager. This may not be acceptable because of privacy or security concerns. By design, items that are sent by a delegate cannot appear in someone else's Sent Items folder.
A solution is for the manager to grant permissions to their Sent Items folder to the delegate. The delegate can then move or copy the items from their own Sent Items folder to the manager's Sent Items folder after they open the manager's mailbox as an additional mailbox. To do this:
Outlook 2002 and Outlook 2003
Outlook 98 and Outlook 2000NOTE: Outlook must be installed in Corporate or Workgroup (CW) mode.
(https://support.microsoft.com/kb/291626/ )How to Manage Multiple Exchange Mailbox Accounts
(https://support.microsoft.com/kb/196996/EN-US/ )OL2000: (CW) How to Manage Multiple Exchange Mailbox Accounts
(https://support.microsoft.com/kb/289993/EN-US/ )OL2002: Private Meeting Requests Are Not Sent to Delegate Even Though Delegate Can See Private Items
(https://support.microsoft.com/kb/299590/ )OL2002: Error Message: "You Cannot Schedule a Meeting with <Resource Name> Because You Do Not Have the Appropriate Permissions"
Article ID: 317865 - Last Review: May 1, 2009 - Revision: 6.0