Shulou(Shulou.com)06/02 Report--

In daily work, there are often scenarios of using shared mailboxes (that is, multiple people access a mailbox), usually mailboxes created on a department or project basis. In such scenarios, the early version of Exchange 2010 is implemented [temporarily named as traditional shared mailbox] by creating a user mailbox and multiple people know the username and password of the mailbox, and then configure the mailbox on Outlook so that messages sent to the shared mailbox or emails sent using the shared mailbox can be seen by all authorized personnel. A shared mailbox [Share mailbox] type has been introduced after Exchange 2013. This type of mailbox can be authorized to multiple people or groups, and the account of Share mailbox is a Disabled User in AD. In other words, Share Mailbox cannot log in directly, and can only view the data in the shared mailbox through other mailboxes by granting permissions. The implementation of Share Mailbox mailbox is temporarily named as modern shared mailbox here.

The disadvantage of the traditional shared mailbox is the password management of the shared mailbox. It is very troublesome to update the password at one time to inform all the relevant personnel who have permission.

Although the modern shared mailbox solves the problem of account password management, it is also faced with another problem, that is, when the authorized mailbox user sends an email in the name of Share mailbox, it cannot be found in the "sent mail" of Share Mailbox itself, and can only be seen in the "sent mail" of the mailbox that sent the mail. [this situation also applies to the delegation of mailbox permissions, and such questions are also sent. For example: mailbox An and mailbox B, mailbox A has the permission to send mail on behalf of mailbox B, but when mailbox A sends a lot of mail on behalf of mailbox B, mailbox B actually does not know what mail mailbox A sent, unless the recipient replies to the email after receiving the email]

Then the problems mentioned above have been solved after Exchange 2016 CU6. We can selectively turn on the outbox mail copy function by using the common parameters MessageCopyForSentAsEnabled and MessageCopyForSendOnBehalfEnabled.

The specific demonstration results are as follows:

To verify this functionality, I first created a Share mailbox, and then gave the other two mailboxes full control and Send As permissions, respectively. Then use any of the authorized mailboxes to send messages using Share Mailbox, and then observe whether the sent messages are synchronized to other mailboxes.

1. First create a shared mailbox named testtest.

2. Give mailtest01 and temp01 mailboxes full access and SendAs permissions to the shared mailbox testest.

3. Enable the MessageCopy function by calling Set-Mailbox-Identity testtest-MessageCopyForSentAsEnabled $true.

4. Log in to OWA using mailtest01, add a shared mailbox, and then send a test email [sender is testtest].

5. Check that the "sent mailbox" has been synchronized in the mailboxes of mailtest01 and Testtest [ShareMailbox].

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.