How to check email queue on Exchange 2010/2013/2016/2019

Microsoft Exchange Server is a workhorse of today’s mail delivery systems. Depending on the size of the organization, it can send tens or even hundreds of messages every minute. Therefore, it is good to know how to quickly check an email queue on your Exchange 2010, 2013, 2016 or 2019. This is specifically useful to determine if the mailflow is fluent, how many messages are waiting to be processed or whether emails are not stuck in the queue.

Queue Viewer lets you check the email queue on your Exchange server 2016/2013/2010.

Types of email queues

There are basically three major types of queues available on MS Exchange Servers:

  • Submission queue – contains messages waiting to be processed by transport agents
  • Unreachable queue – contains email that could not be delivered to their destination
  • Poison message queue – holds messages classified as dangerous for the server.

Usually, the submission queue is the most important as it is responsible for the actual mail delivery. If the submission queue stalls, no messages reach their intended recipients.

How to check the content of an email queue?

To check the contents of the submission queue run the following command in the Exchange Management Shell on your Exchange 2016/2013/2010:

Get-Queue -Identity Submission | Select Identity,Status,MessageCount

The result of the Get-Queue command is piped (redirected) to the Select command. This command shows only the Identity, Status, and MessageCount parts of the submission queue properties. In the example below, the submission queue shows 778 messages waiting to be processed.

Using PowerShell, you can check how many email is waiting in the submission queue.

If you want to see all available details describing the submission queue, simply run the same command but without the Select part:

Get-Queue -Identity Submission

The result:

Run PowerShell cmdlet to see all available details describing the submission queue.

The above method is simple, quick and effective as it can also be used with the remotely connected PowerShell session.

Suggested reading:

Tools for Exchange Server

Recommended articles

Exporting messages from mail queues on Exchange 2010/2013/2016/2019

Exporting messages from mail queues on Exchange 2010/2013/2016/2019

When a company migrates mailboxes between Exchange servers, they run the risk of losing emails that were in message queues. The gravity of this problem increases with the size of the organization and the amount of mail traffic - when hundreds of emails are sent every hour, the danger of overlooking them during the switch is quite high. Fortunately, a simple PowerShell script is all you need to avoid the setback. It is even useful as a final checkup measure before decommissioning the old server. Below you'll find steps required to perform this task.
How to quickly verify if Autodiscover is working

How to quickly verify if Autodiscover is working

There are two quick ways to check if Autodiscover is working: Outlook & PowerShell. I'm explaining both.
Managing users’ Outlook rules from Exchange Management Shell (with PowerShell)

Managing users’ Outlook rules from Exchange Management Shell (with PowerShell)

Outlook rules (or inbox rules) can be controlled with PowerShell. Here's how.

Comments

  1. Any idea how to simulate slowness in the mail queue? I am working on a way to monitor this and would like to be able to test. Thanks

    • avatar
      Adam the 32-bit Aardvark says:

      Hi Daniel,

      We (CodeTwo) don’t offer one and I can’t really suggest 3rd party software. But there has to be at least one free Exchange monitoring tool that provides queue info somewhere on the web :)

      All the best,
      Adam

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

*

CodeTwo sp. z o.o. sp. k. is a controller of your personal data.
See our Privacy Policy to learn more.