The issue with this not working for mailboxes in different AD Sites is resolved. A fix is available from Microsoft CTS for this issue. Please open a case and request the fix for this if you need it.
There are many scenarios and business requirements that are addressed by the use of the Send As, Send on Behalf of and Full Mailbox Access capabilities. These permissions can be easily assigned using the Exchange Management Console or the Exchange Management Shell. The particular permissions of interest for this blog post are the Send As and the Send on Behalf of permissions. Once these permissions are assigned, every e-mail that is sent using either one of these permissions is saved in the Sent Items folder of the sender, by default. The ability to change this behavior using a registry key, the DelegateSentItemsStyle is discussed in KB953804 for Outlook 2003 and KB972148 for Outlook 2007. When the DelegateSentItemsStyle registry key value is set to ‘1’, the behavior changes and the items are now saved in the Sent Items folder of the mailbox that the permissions were assigned for. As an example if User 1 has Send As permissions on User 2’s mailbox, whenever User 1 send as e-mail as User 2, the item is saved in the Sent Items folder of User 2, instead of User 1’s Sent Items Folder. One of the requirements for this registry key to work correctly is to run Outlook in cached mode. If you run Outlook in Online Mode, the results are inconsistent.
We are introducing a major change with Exchange Server 2010 SP2 RU4. To explain the change, let me first set the stage with an example. The user “Delegate” has been assigned Full Mailbox Access and Send As permissions to the user “Manager” mailbox. This is accomplished using the below powershell cmdlets.
Add-ADPermission -identity Manager -User Delegate -ExtendedRights "Send As”
Add-MailboxPermission Manager -User Delegate -AccessRights FullAccess -InheritanceType all
With Exchange Server 2010 SP2 RU3 and lower, whenever Delegate would use Send As permissions and send an e-mail to any user, the item would show up in the Sent Items Folder of Delegate. With Exchange Server 2010 SP2 RU4, this behavior changes. We can now make a copy of the e-mail in the Sent Items folder of the Manager Mailbox. To achieve this functionality we are introducing 2 new powershell cmdlets;
A sample default output of the Get-MailboxSentItemsConfiguration is below. This has been executed against the Manager mailbox
[PS] C:\Windows\system32>Get-MailboxSentItemsConfiguration Manager
RunspaceId : 38eb470d-f92d-4381-afa0-5bb7b8741e02
SendAsItemsCopiedTo : Sender
SendOnBehalfOfItemsCopiedTo : Sender
IsValid : True
Note, the values for SendAsItemsCopiedTo and SendOnBehalfOfItemsCopiedTo. Both attributes have the default value of Sender. The attributes can be configured with any one of three possible values; Sender (Default), SenderAndFrom or From
Let me quickly explain what each of these values mean
IMPORTANT: At this time, the From value does not work as expected. It performs the same action that the SenderAndFrom value implies, which saves the e-mail in both, the Manager and Delegate Sent Items folder. We are NOT recommending that customers use the From value at this time. The intended functionality of this value is planned to be included in a future release of a RollUp or Service Pack for Exchange Server 2010.
Now, I will use the Set-MailboxSentItemsConfiguration and set the Manager Mailbox SendAsItemsCopiedTo attribute value to SenderAndFrom
[PS] C:\Windows\system32>Set-MailboxSentItemsConfiguration Manager -SendAsItemsCopiedTo SenderAndFrom
SendAsItemsCopiedTo : SenderAndFrom
Once this change is made, all e-mails that Delegate user sends using Send As permissions on the Manager user will show up in the Sent Items folder of both, Manager and Delegate. An important point to note is that we no longer require the DelegateSentItemsStyle registry key to be present or set with a value. We also do not require that Outlook be configured to be running in Cached Mode. This change allows Outlook to be running in Online Mode to achieve the required functionality.
We are also introducing this as a self-service option for end users! Users will have the ability to use Outlook Web App (OWA) to set the values as well! Below is a screenshot of the Options in OWA.
IMPORTANT: For this to work, we require that all Client Access Server roles in the Site where the users Mailboxes are created be updated to Exchange Server 2010 SP2 RU4. We also require that all Mailbox Servers that host the mailboxes that require this functionality be updated to Exchange Server 2010 SP2 RU4
I hope that you find the information above useful!
Is there a planned date for fixing the From-Only option?
This would really make me a very happy person!
@Gijs: There is no planned date at this time for the From option to work as expected, which is to make a copy of the e-mail ONLY in the shared mailbox sent items folder. We strongly recommend that customers do NOT use this setting at this time. You should only use the SenderAndFrom setting
@Alberto Diaz: Essentially this setting will take effect only when the user's mailbox has been provided Full Mailbox Access or Send-As permissions to another user. I will investigate if it is possible to disable changing this setting in OWA and post back
I noticed that the "Sent Items" option in OWA does not seem to be localized (we are running a german environment). I double-checked to make sure that I installed the german version of the roll-up, which I did. :)
Still, the "Sent Items" screen in the ECP appears in english.
I have been playing with Exchange 2013 RTM in my lab, and this long awaited feature is not there. It is not in the OWA interface and there is no powershell cmdlet called Get-MailboxSentItemsConfiguration either. Do you have any info regarding that ?
@starman: There are plans to port this feature over the Exchange 2013, we do not have an ETA at this time.
I have updated the blog post with information that the fix for cross site mailboxes is available. Please open a case with Microsoft and request the fix.
@Teck: I will check with the OWA team and let you know in localization of the screen for other languages and when it will be available and post back
Is it possible to set this option for a database or the server, to always use this option. Now it seems you have to do this for every existing and new mailbox.
Is it possible to make this work for a delegated Distribution Group as well?
Whe a Dsitribution Group has "SendOnBehalf" permission on a delegated mailbox and the individual members are al set to "SenderAndFrom" the mail will NOT be placed in the Sent Items of the delegated mailbox.
Only when I give the individual members "SendOnBehalf" permission, this option works fine.
Will the be a workarround for this behaviour?
Is Microsoft developing simular functionality for the Deleted-Items in On-line mode, as already developed for Outlook in Cached mode with the registry setting "DelegateWasteBasketStyle"?
Is there any option that I can track and find all the emails that are sent from a shared mailbox using the Send As permission.
We have one shared mailbox called "customers" and around 50 users are having send as permissions for that. All users have to reply back using this shared mailbox to all their customers. All users are sending emails 24*7 in 3 shifts...so the manager wants to calculate the sent count using this shared mailbox as "send as" of each users per shift basis for one day and this needs to be emailed automatically
@Patry You can set this option for all the mailbox in databases are server using the below option
Get-Mailbox -ResultSize Unlimited -Database "Database Name"| Set-MailboxSentItemsConfiguration -SendAsItemsCopiedTo SenderAndFrom
Get-Mailbox -ResultSize Unlimited -Server "Server Name"| Set-MailboxSentItemsConfiguration -SendAsItemsCopiedTo SenderAndFrom
@Rajkumar. Sorry for the late reply but....THANKS !!
Just like Harrie, I'd love to know if there will be a DelegateWasteBasketStyle feature added as well. With outlook 2013 coming out, I'm cranking out our group policy settings and would like to not have to push those possibly not supported registry settings.