[Migrated from MSDN Exchange Dev] MessageCopyForSentAsEnabled not applying

KyleXu-MSFT 26,211 Reputation points
2020-12-11T06:14:33.993+00:00

Exchange 2016 CU12 - messages sent as shared mailbox or user mailbox are not copied to the shared mailbox / sender mailbox sent items, with MessageCopyForSentAsEnabled $True

I've gone trough all google hits, none of them working. Any suggestions?

Source link: https://social.msdn.microsoft.com/Forums/office/en-US/d54e338a-0651-4337-90d1-da7e2c099c2c/messagecopyforsentasenabled-not-applying?forum=exchangesvrdevelopment

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,356 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. KyleXu-MSFT 26,211 Reputation points
    2020-12-11T06:22:53.953+00:00

    Do you try to send emails from the OWA?

    When you send as a shared mailbox, this email will show in your mailbox Sent Items by default. If you want this email could also show in shared mailbox, you need to enable the "MessageCopyForSentAsEnabled" on shared mailbox rather than your mailbox. I would suggest you check the configuration again.

    Get-Mailbox YourShared | fl MessageCopyForSentAsEnabled  
    

    When you send email from Outlook client, if there exist multiple mailboxes in this profile, you need to choose the email address that between the horizontal line, those email addresses are the send as email address(Will appear after the first use):
    47283-qa-kyle-14-29-20.png
    If you select the address above the horizontal line, the email will be sent directly from the this mailbox rather than sent in the way of "send as".


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments