Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Shared mailbox sent mail lands only in my own Sent Items: saving a copy in the shared mailbox

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

When you send or reply as a shared mailbox, Outlook sends the message from your own account, so the copy is stored in the Sent Items folder of your mailbox, not the shared one. Microsoft documents two fixes. The first is a setting on the shared mailbox in Exchange PowerShell, and it is the only one that works in new Outlook. The second is a registry value on each Outlook client.

Which command you need depends on how people send: MessageCopyForSentAsEnabled for Send As, MessageCopyForSendOnBehalfEnabled for Send on Behalf.

What the error means

This is behaviour rather than an error message. Microsoft's page, "Messages sent from a shared mailbox aren't saved to the Sent Items folder", describes it for Outlook 2016 or later where you've been "delegated permission to send email messages as another user or on behalf of another user from a shared mailbox". The sent message "isn't saved to the Sent Items folder of the shared mailbox. Instead, it's saved to the Sent Items folder of your mailbox."

The page gives the reason: "shared mailboxes don't require a license and can't be added to Outlook as independent mailboxes. You can't sign in to a shared mailbox. Instead, you sign in to your own mailbox, and then you open the shared mailbox." When you send or reply from the shared mailbox, "Outlook automatically sends or replies from the sender's account."

Microsoft's shared mailbox overview says the same about access: delegate access is done "through the delegate's own mailbox", and the shared mailbox itself needs no separate licence for access. The page applies to Exchange Online, and its commands also name on-premises Exchange Server.

Likely causes

The behaviour has one cause. What varies is which sending permission the staff use and which Outlook they run.

Cause What you see How to confirm
Sending with Send As and the shared mailbox is not set to copy Message appears in the sender's Sent Items only Get-Mailbox on the shared mailbox shows MessageCopyForSentAsEnabled as False
Sending with Send on Behalf and the shared mailbox is not set to copy Same, and the From line reads sender on behalf of mailbox MessageCopyForSendOnBehalfEnabled is False
Registry value DelegateSentItemsStyle set on some PCs and not others Some people's mail is saved in both places, some in one Value present or absent under the Outlook Preferences key
Mixed Outlook versions Registry method works in classic Outlook but not in new Outlook Microsoft: "If you're using new Outlook, only Method 1 will apply."

Prove the cause before changing anything

  1. Check how staff send. Microsoft separates Send As (the message looks as if the shared mailbox sent it) from Send on Behalf (the message reads "John on behalf of Reception Building 32", in Microsoft's example).
  2. In Exchange Online PowerShell, read the current values on the shared mailbox. The cmdlet is on Microsoft's Get-Mailbox page; the two property names are on its Set-Mailbox page:
Get-Mailbox -Identity support@contoso.com.au | Format-List MessageCopyForSentAsEnabled,MessageCopyForSendOnBehalfEnabled
  1. Record both values. False is the default for each, according to the Set-Mailbox page.
  2. List who holds Send As on the shared mailbox. Microsoft's Get-RecipientPermission page shows this form, which "lists the users who have SendAs permission on the mailbox":
Get-RecipientPermission support@contoso.com.au

Send on Behalf is held separately, in the GrantSendOnBehalfTo property of the mailbox, which Microsoft says is blank by default so that "no one else has permission to send on behalf of this mailbox." Full Access alone is not enough to send. The shared mailbox page says a user with Full Access "can't send email from the shared mailbox unless they also have Send As or Send on Behalf permission."

  1. On one affected PC, check whether the registry value exists:

HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Preferences

Look for a DelegateSentItemsStyle DWORD. Do not create it yet.

Fix

Method 1: set the mailbox to keep a copy (applies to new Outlook as well).

Save first: you already recorded the current values in step 3 above. They are the values to restore.

Disruptive step: the commands below change the mailbox so that, from now on, a copy of each message also goes where the page says, and mailbox storage grows by the size of those copies.

For mail sent as the shared mailbox, run:

Set-Mailbox -Identity support@contoso.com.au -MessageCopyForSentAsEnabled $True

For mail sent on behalf of the shared mailbox, run:

Set-Mailbox -Identity support@contoso.com.au -MessageCopyForSendOnBehalfEnabled $True

These are Microsoft's commands, with the placeholder replaced by an example name.

To undo it, run the same command with $False, or with the value you recorded. Mail already copied stays where it is.

Note the wording difference. Microsoft's page says the setting saves "a copy of the message to the Sent Items folder of the shared mailbox". The Set-Mailbox parameter reference describes the $true value as sending "a copy of the message ... to the sender's mailbox". The two pages word this differently, and neither explains the difference. Settle it by test: after the change, send one message and look at both Sent Items folders.

Method 2: registry value on the Outlook client (classic Outlook only, cached mode required). Microsoft's page says the option works only if Outlook "must be configured to run in Cached Exchange mode". It also warns to back up the registry first.

Save first: in a Command Prompt on that PC, signed in as the affected Windows user, export the Preferences key to a .reg file (the folder C:\Temp must exist), and note whether the DelegateSentItemsStyle value was already there:

reg export "HKCU\Software\Microsoft\Office\16.0\Outlook\Preferences" C:\Temp\outlook-preferences-before.reg

Risk: the registry steps below add a value, and a wrong registry edit can break Outlook for that profile. Impact: applies to that Windows user only.

Steps from the page: open Registry Editor, go to the key above, choose New, then DWORD 32-bit Value, name it DelegateSentItemsStyle, set Value data to 1, and close. Microsoft links an issue where "Email remains in the Outbox when you use the DelegateSentItemsStyle registry value", so test before rolling it out.

To undo it: if the value did not exist before your change, delete it:

reg delete "HKCU\Software\Microsoft\Office\16.0\Outlook\Preferences" /v DelegateSentItemsStyle

Importing the saved file does not remove a value that was not in it, so use the import only when the value existed before and you need its old data back: reg import C:\Temp\outlook-preferences-before.reg.

If you use both methods, Microsoft's table says what to expect:

DelegateSentItemsStyle MessageCopyForSentAsEnabled Result
0 True One copy in the sender's mailbox and one in the shared mailbox
1 True Two copies in the shared mailbox and none in the sender's mailbox
0 False A copy in the sender's mailbox only
1 False A copy in the shared mailbox only

Confirm the fix

Send one test message as the shared mailbox from a normal staff PC, then open both Sent Items folders. Check the row in the table above that matches your settings. Repeat for Send on Behalf if you use it. Test from new Outlook and classic Outlook if both are in use. If a message still lands only in the sender's own Sent Items, check the From line of that message: a message sent from the person's own address is not a message from the shared mailbox, and no shared-mailbox setting applies to it. Then check whether that person sends with Send As or with Send on Behalf, and confirm the matching command was the one you ran.

Example (illustrative): support@contoso.com.au is used by six people, each sending about 25 messages a day as the mailbox. That is 150 messages a day (6 x 25), or 750 in a five-day week, all missing from the shared Sent Items. A colleague covering for someone on leave can see none of them. After MessageCopyForSentAsEnabled is set to $True, Microsoft's Learn page says a copy is saved in the shared mailbox, so the team expects new messages there; they confirm it by sending one test message and looking in both Sent Items folders. Messages sent before the change are not copied.

What to watch afterwards

  • Add the setting to the shared mailbox creation checklist, so new shared mailboxes behave the same.
  • If you combine the registry value and the mailbox setting, re-test after Outlook updates. Two copies in the shared mailbox is the documented result for 1 plus True.
  • Check that the shared mailbox is not hidden from the address list. Microsoft says Send As and Send on Behalf "do not work in the Outlook desktop client" with HiddenFromAddressListsEnabled set to True.
  • Watch mailbox size. Microsoft's About shared mailboxes page (dated 2026-03-13) says a shared mailbox can hold up to 50 GB without a licence, and that when it reaches the limit "you can't send new email." Limits and licence terms change, so check the current page.

Risks and limits

These commands have not been run or lab-tested. Microsoft's page gives no figure for how long the setting takes to apply; test after saving. The registry method needs classic Outlook in Cached Exchange mode and does not apply to new Outlook. Microsoft's Set-Mailbox page says both copy parameters are "not available for linked user mailboxes".

Keep Send As and Send on Behalf permissions as small as the work needs. A copy of every message in the shared mailbox is visible to everyone who has access to it, so check what staff send before turning it on.

Sources