Even in a properly functioning Exchange 2003 SMTP queue, corrupt messages can become stuck and cause mail flow issues. Performance Monitor (Perfmon) is a tool within Exchange Server Setup that can be configured to alert administrators when any SMTP queues in an Exchange 2003 environment reach a designated threshold. By monitoring the server for corrupt messages or denial-of-service attacks, administrators can circumvent SMTP message queue problems and email delivery failures. This tip by Exchange MVP Brien Posey explains how.
If Exchange Server 2003 SMTP queues are working properly, corrupt messages occasionally may become stuck in a queue. This can cause the queue to fill up and prevent mail flow until the damaged messages are removed. The process of removing damaged email from an SMTP queue is simple; however, Exchange Server doesn't alert administrators when a message becomes stuck. Typically, delivery of user email simply stops.
Microsoft and other third-party vendors offer solutions that detect message queue back-up failures. Such applications tend to be expensive and beyond the scope of small or medium-sized enterprises (SMBs). An alternative is to configure the Performance Monitor to alert you of message queue problems.
When Exchange Server is initially deployed, the Setup program installs various Exchange-specific Performance Monitor objects. Similar to the default counters in Microsoft Windows, these counters enable you to measure different aspects of Exchange Server performance.
The Send Queue Size counter monitors Exchange Server message queues. This tool is located wit
To continue reading for free, register below or login
To read more you must become a member of SearchExchange.com
hin the MSExchangeIS Mailbox performance object. But before you can configure the server to detect message queue problems, you must monitor this counter to determine the maximum number of messages per queue under normal circumstances. Watch this counter during periods of peak usage. Additionally, this counter is storage group-specific, so you will have a separate instance of the counter for each storage group.
Once you've determined average queue length, you decide what value might indicate queue problems. For example, if there are 20 messages in the queue every Monday at 8 a.m ., you might conclude that 40 messages in the queue would indicate a problem. Whatever value you decide on, be sure to leave some room for unexpected usage spikes and future business growth.
Once you've determined a threshold value, configure the Performance Monitor to trigger an alert if values exceeded this level:
About the author: Brien M. Posey, MCSE, is a four-time recipient of Microsoft's Most Valuable Professional Award for his work with Windows Server, Internet Information Server (IIS) and Exchange Server. Brien has served as CIO for a nationwide chain of hospitals and healthcare facilities, and was once a network administrator for Fort Knox. You can visit Brien's personal Web site at www.brienposey.com.
Do you have comments on this tip? Let us know.
Please let others know how useful this tip was via the rating scale below. Do you know a helpful Exchange Server, Microsoft Outlook or SharePoint tip, timesaver or workaround? Email the editors to talk about writing for SearchExchange.com.
