amset.info
from Sembee Ltd.
UK MS Exchange Consultants

Exchange - Net Admin - Outlook
Windows Mobile - Windows

Contact - Director's Blog

AddThis Social Bookmark Button


Exchange Server Home

Exchange Consultancy

Exchange Resources


Microsoft Exchange
Amazon Store


Basic Email Gateway Server

Company wide Contact List

Disabled User Account

Distribution Lists

DNS Configuration

Exchange and a
Dynamic IP Address

Event ID 1221

Filter Unknown Users

Global Mailbox Folder
Permissions from Server

Intelligent Message Filter

Internal Email Address
for External People

Mailbox and Management
Account

Message Tracking

Migrating to a new server

Multiple Domains

Offline Address Book Errors

Options when a Staff Member
Leaves

Outlook Web Access

PDAs, OMA and EAS

Permissions Best Practises

Post Install Configuration

Public Folders

Prerequisites for Exchange
System Tools

RPC over HTTPS

Secure your SMTP Relay

Shutdown Script

SMTP Services and Exchange

SMTP Diagnostics

Spam Cleanup

Switching From POP3
to SMTP Delivery

Telnet Test

Username Change

Microsoft Exchange Server
Page Last Reviewed: 15/02/2009

Exchange Server
Compatibility Information
Exchange
Server Version
Compatibility
5.5 Yes
2000 Yes
2003 Yes
2007 Yes
SMTP Diagnostics

Author: Simon Butler, Exchange MVP, MCSE

One of the common problems that an Exchange administrator has to deal with is the failure of outbound external messages to be delivered. This will cause complaints from the senders and can cause issues with the server itself.

As a minimum you should keep an eye on the queues, as this can indicate whether there is a problem. There are monitoring tools within Exchange that can alert you to messages in the queues, but watch the thresholds carefully or you will get false positives.

Collecting the Evidence

There are a number of bits of information that you can collect which help with diagnosing problems.

  • The Non-Delivery Report (NDR)
    This is the most important item as it will show the SMTP diagnostic code. If the users are complaining, ask them to send you the complete NDR so that you can see what the server reported as the problem.
  • Message Tracking Logs.
    Exchange can track what it did with the message. This needs to be enabled before the problem, and as it has such a low overhead, it is a good idea to have it running all the time, retaining at least 30 days worth of logs. More Information.
  • SMTP Diag tool.
    This is a download from Microsoft and can tell you loads about the SMTP status as seen by the Exchange server.
    http://www.microsoft.com/downloads/details.aspx?FamilyID=BC1881C7-925D-4A29-BD42-71E8563C80A9&displaylang=en
  • SMTP Logs.
    The logs that the SMTP server creates are limited but can show if the connection was made. Enable the logging in ESM, Servers, <your server>, Protocols, SMTP. Right click on the SMTP Virtual Server and choose Properties. The logging settings are on the first tab.

Problems with Inbound Email
Inbound email diagnostics is limited, there are a few things that you can do though.

Problems with Outbound Email
There are lots of tools for outbound diagnostics and your server can give you lots of data to look at the problem.

Last Page Update:
15/02/2009

More Content from Sembee Ltd.
 
Resources on amset.info Other Sites Sembee Ltd.
Microsoft Exchange Command Prompt Getting Started Guide Microsoft Exchange Consultancy
Microsoft Outlook Login Scripts Director's Blog
Network Administration MS Exchange Resources  
Internet Explorer Knowledge Base search  
Microsoft Windows Recovery of MS Office content from Temp Files  
Microsoft Windows Mobile Troubleshoot the Automatic Updates Client  
Amazon Store UK ISP Status Pages  

© Sembee Ltd. 1998 - 2010.

Reproduction of any content on this web site is prohibited without express written consent. Use of this web site is subject to our terms and conditions. All trademarks and registered trademarks are property of their respective owners. This site is not endorsed or recommended by any company or organisation mentioned on this site. This site is to provide guidance only and as such we cannot be held responsible for any consequences of following the advice given.