You want to create mailboxes in Exchange Online and use Office 365. Before you can…
Test internal mail flow in Exchange Server 2016
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.
Table of contents
Information
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.
Send message to internal recipient
Start Outlook client and configure Outlook. In my example, the user is James. Fill in the To… field to which you are going to send the message. 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.
Verify delivery receipt
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’s 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 ensure that the mail flow is working as expected in the Exchange organization.
Read more: Exchange 2016 internal mail flow not working »
Conclusion
In this article, you learned how to test internal mail flow in Exchange Server 2016. You can test internal mail flow 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.
This Post Has 0 Comments