You did remove full access permission from a user or shared mailbox, which is automapped.…
After setting up Exchange Server 2016, it’s time to test the internal mail flow in Exchange Server 2016. You can do that through the Outlook client or Outlook Web Access (OWA). Both will work. In my example, we are going to use Outlook client.
Test internal mail flow in Exchange Server 2016
Make sure that you have already set up a couple of test mailboxes. If you don’t, you can’t email to an internal mailbox.
Start Outlook client and configure Outlook. In my example, the user is James. Fill in the To… field which you are going to send the message to. In my example, it’s Amanda. Amanda is an internal colleague of James.
Set a delivery receipt so that the system will notify him whether that message could be received by the user Amanda. Click Options in the tabs and enable Request a Delivery Receipt. Click Send when done.
Keep an eye on the mailbox. The delivery receipt did come back telling that the mailbox receives the email. The Exchange 2016 server was able to generate and send a delivery to James his mailbox. Mail is flowing in both directions just fine.
If you want to double-check, log in with Amanda her mailbox and check the email from James.
Now, if you like to test more mailboxes in different databases, you can do that. Create test mailboxes and send some test emails to make sure that the mail flow is working as expected in the Exchange organization.
What if the internal mail flow is not working as expected? Read the article Exchange 2016 internal mail flow not working.
I hope that this article helped you to test internal mail flow in Exchange Server 2016.
In this article, you learned how to test internal mail flow in Exchange Server 2016. You can do the internal mail flow testing for other Exchange servers too. For example, Exchange Server 2010/2013/2016/2019. Want to test mail flow with PowerShell? Make use of the Test-Mailflow cmdlet.
Did you enjoy this article? You may also like Export Let’s Encrypt certificate in Windows Server. Don’t forget to follow us and share this article.