Troubleshooting Message Flow in Microsoft...

Troubleshooting Message Flow in Microsoft® Exchange 2000 Server—A Step-by-Step Approach

White Paper

Published: August 2001

Troubleshooting Message Flow in Microsoft Exchange 2000 Server—A Step-by-Step Approach 1

Table of ContentsIntroduction.......................................................................................................2

Step 1: Check Internet Message Format Settings.................................................................2

Step 2: Ensure Recipient Policy Settings Are Correct............................................................3

Step 3: Configure Default SMTP Virtual Server Settings.......................................................5

Step 4: Verify Address Spaces and Delivery Options on SMTP Connectors.........................10

Step 5: Verify DNS Settings................................................................................................12Settings on the Server Running Exchange.....................................................................12Settings on the DNS Server............................................................................................13

Step 6: Verify SMTP Port Settings.......................................................................................14

Step 7: Use Message Tracking............................................................................................16

Step 8: Use Event Viewer...................................................................................................16Configuring Diagnostic Logging.....................................................................................17

Additional Resources..........................................................................................................18


Troubleshooting Message Flow in Microsoft Exchange 2000 Server—A Step-by-Step Approach White PaperPublished: August 2001

For the latest information, please see http://www.microsoft.com/exchange/

IntroductionMaintaining efficient message flow within a messaging system is a top priority for administrators. The information in this document will help you resolve some of the most common message flow issues you may encounter with your messaging system, such as undeliverable mail and growing message queues. This document also serves as a starting point for troubleshooting mail flow problems caused by improper configurations. By verifying configuration settings, you should be able to get your initial installation of Microsoft® Exchange 2000 Server sending and receiving Internet and local e-mail. You should also be able to significantly reduce the amount of time it takes to manage any message flow issues you may experience.

Step 1: Check Internet Message Format SettingsEnsure that the Simple Mail Transfer Protocol (SMTP) domain is set to asterisk (*) (meaning, all domains), which is the default SMTP domain. It is recommended that you keep this default setting. The default SMTP virtual server uses the * domain. After you install Exchange 2000 Server Service Pack 1 (SP1), the default SMTP domain setting of * cannot be changed.You may add additional domains, but the * domain must always be present. If you decide to add a domain, do not add your own local domain or any domains for which this server running Exchange is responsible for holding records. Adding such a domain causes local mail delivery to fail. For the purposes of this document, the only domain listed in SMTP domain should be *.To ensure your SMTP domain is set to *1. Click Start, point to Programs, point to Microsoft Exchange, and then click

System Manager.2. In the console tree, double-click Global Settings. 3. Double-click Internet Message Formats.4. In the details pane, right-click Default, and then click Properties. 5. Ensure that SMTP domain is set to *.


Step 2: Ensure Recipient Policy Settings Are CorrectExchange uses recipient policies to determine which messages to route internally to mailboxes in your organization. Improperly configured recipient policies can disrupt message flow for some or all recipients in your messaging system. To ensure that your recipient policies are properly configured, verify the following: Verify that recipient policies do not contain an SMTP address that matches the

fully qualified domain name (FQDN) of any servers running Exchange in your organization. For example, if you have @yourservername.yourdomainname.com listed as an SMTP address and as a domain name on any recipient policy, it prevents mail from routing to other servers in the routing group.

Verify that the domain for which you want to receive SMTP mail is listed on a recipient policy—either on the default policy or another recipient policy. Verifying that the domain that you want to receive SMTP mail for is listed on a recipient policy ensures that your users can receive mail from other SMTP domains.

Verify that you configured the necessary SMTP e-mail addresses to receive e-mail for additional domains. If you are not receiving e-mail between your SMTP domains, you may need to configure additional SMTP addresses for your recipients. For example, some of your users may currently receive mail addressed to contoso.com and you also want to them to receive mail addressed to adatum.com.

To verify that your recipient policies do not contain addresses that match the FQDN1. Click Start, point to Programs, point to Microsoft Exchange, and then click

System Manager.2. In the console tree, double-click Recipients, and then double-click Recipient

Policies. 3. In the details pane, double-click a recipient policy configured on the server.4. On the E-Mail Addresses (Policy) tab of that policy, view the SMTP

addresses configured by that policy and ensure that none of the SMTP addresses match the FQDN of any servers running Exchange in your organization.

5. Repeat steps 3 and 4 of this procedure for each recipient policy configured on this server.

For more information, see Q288175 “XCON: Recipient Policy Cannot Match the FQDN of Any Server in Organization” in the Microsoft Knowledge Base.

Important By default, the SMTP domain name is the name of the domain in which Microsoft Active Directory™ directory services resides. This default SMTP domain name is not always the same name you want to use for SMTP mail.For example, if your organization is a large distributed corporation, you can use a unique SMTP address format for each division to make e-mail addresses for recipients in each division distinct. For example, in a distributed organization, users in different divisions at a company called

http://go.microsoft.com/fwlink/?LinkId=3052&ID=288175


Blue Yonder Airlines might have addresses such as: <alias>@Administration.blueyonderairlines.com and <alias>@Marketing.blueyonderairlines.com.

To verify that your users can receive e-mail from other SMTP domains1. Click Start, point to Programs, point to Microsoft Exchange, and then click

System Manager.2. In the console tree, double-click Recipients, and then double-click Recipient

Policies. 3. In the details pane, double-click a recipient policy configured on this server. 4. On the E-Mail Addresses (Policy) tab of that policy, view the SMTP

addresses configured by that policy and ensure that the domain that you want to receive SMTP mail is listed as an address. Verify that the check box next to the address is selected.

5. Double-click that SMTP address, and verify that the This Exchange Organization is responsible for all mail delivery to this address check box is selected.Note If you have more than one recipient policy configured on a server, the SMTP e-mail address you are trying to verify may be located on another recipient policy.

6. If you have more than one recipient policy configured on a server, repeat steps 3 through 5 in this procedure for each recipient policy configured on this server.

To configure the necessary SMTP e-mail addresses for your users1. On the Start menu, point to Programs, point to Microsoft Exchange, and

then click System Manager.2. In the console tree, double-click Recipients, and then double-click Recipient

Policies. 3. In the details pane, double-click the recipient policy you want to modify. 4. On the E-Mail Addresses (Policy) tab, click New, and then double-click

SMTP Address.5. In Address, type the information required by the address type you selected,

for example, to route mail to A. Datum Corporation, type @adatum.com.6. Ensure that the This Exchange Organization is responsible for all mail

delivery to this address check box is selected.7. To keep track of information about the recipient policy you modified, click the

Details tab. In Administrative note, type information about the address you added to the recipient policy.

8. On the E-Mail Addresses (Policy) tab in Generation rules, select the address you added, and then click Apply.

Important When you click Apply, Exchange may prompt you to update all corresponding recipient e-mail addresses to match the changes you made. If you click Yes, the changes made to the


recipient policy are applied to the recipients defined for the policy on the next cycle of Recipient Update Service. E-mail addresses previously configured for these recipients are demoted to secondary addresses.

If you want this e-mail address to apply to only a subset of users, create a new recipient policy with a filter that selects the subset of recipients you specify. If the filter is too complex or only a small number of users require the additional address, you can create a filter that creates e-mail addresses that apply only to individual recipients.

Caution All internal domains to Exchange should have a recipient policy configured for them, but that recipient policy may not apply to every user. You can add new SMTP e-mail addresses; however, it is imperative that you do not set SMTP e-mail addresses to match your own local domain. Setting SMTP e-mail addresses to match your own local domain causes mail to stop flowing both remotely and locally.

For information about configuring recipient policies, see Q260973 "XCON: Setting Up SMTP Domains for Inbound and Relay E-Mail in Exchange 2000 Server" in the Microsoft Knowledge Base. For more information about correcting problems with SMTP proxy addresses, see Q140933 "XFOR: SMTP Proxy Address Generated Incorrectly" in the Microsoft Knowledge Base.

Step 3: Configure Default SMTP Virtual Server SettingsThis section helps you understand some of the most common SMTP virtual server configuration settings. For general information about the options on these and other related dialog boxes, click Help or F1 in any Exchange dialog box. After Exchange is installed, most organizations are able to properly send and receive Internet mail without modifying the settings on the Default SMTP Virtual Server object. The default SMTP server transfers Internet mail. Therefore, changing the SMTP default virtual server settings can cause mail flow problems.

Note This document does not discuss adding SMTP virtual servers. Although adding SMTP virtual servers is possible, the default SMTP virtual server can meet most messaging needs.Caution You should verify your SMTP virtual server settings and be familiar with some of the consequences of specific configuration choices when troubleshooting SMTP-related message flow issues.

To verify SMTP virtual server settings1. Click Start, point to Programs, point to Microsoft Exchange, and then click

System Manager.2. Double-click Servers, double-click <Server Name>, double-click Protocols,

and then double-click SMTP.3. Right-click Default SMTP Virtual Server, and then click Properties. 4. Click the General tab. Verify the following settings for the Default SMTP

Virtual Server:




IP address The default setting is (All Unassigned), and it is recommended that you do not change it unless you want to configure multiple SMTP virtual servers.

Click Advanced to select individual IP addresses if you have either multiple network interface cards (NICs) or multiple IP addresses assigned to a single NIC for this SMTP virtual server to listen on. To select individual IP addresses, click Advanced, and then specify ports other than the default.Note Use the Advanced option carefully. Other servers (on the Internet for example) expect to be able to communicate with your server on the default TCP port 25.

5. Click the Access tab to specify what connections the server will accept or deny. Verify the following settings: In Access control, click Authentication to specify the ways in which

users must be authenticated prior to sending mail to this server. Anonymous access is usually used for servers directly connected to

the Internet. If this setting is selected, other servers on the Internet will not authenticate to this server prior to sending mail. Note If this option is not selected, you might not receive incoming mail from the Internet.

Basic authentication is used by mail clients, such as Microsoft Outlook®, that connect to the server using Post Office Protocol version 3 (POP3) or Internet Message Access Protocol version 4rev1 (IMAP4). Such clients authenticate to the server to send mail. Requires TLS encryption is used if you have a digital certificate,

typically in high-security environments. If Requires TLS encryption is selected, the Default domain is the Microsoft Windows® 2000 domain that the user should authenticate against if he or she does not specify a domain. For more information about TLS encryption, see the Exchange online documentation.

Integrated Windows Authentication is used only by Windows user accounts. User names and passwords are encrypted using the NTLM protocol and are passed to the SMTP virtual server for authentication purposes.Note By default, Anonymous access, Basic authentication, and Integrated Windows Authentication are selected. It is recommended that you use the default settings to allow users to authenticate using the most common methods.

In Secure communication, you can configure a certificate (used for TLS encryption) to encrypt messages as they move from server to server. For more information about TLS encryption, see the Exchange online documentation.

In Connection control, click Connection to selectively allow or deny access to this server based on IP address. Click All except the list below for servers directly connected to the

Internet. List only those hosts that you do not want to receive mail


from. You may include any servers that you consider to be the source of unsolicited e-mail on the Internet.

In Relay restrictions, click Relay to configure restrictions for other computers for relaying e-mail though this virutal server based on IP address. Click Only the list below for servers directly connected to the

Internet. List only those hosts you want to allow to relay mail. If you click All except the list below, your server may appear to be a server that is a source of unsolicited e-mail on the Internet.

If you select the Allow all computers which successfully authenticate to relay, regardless of list above check box, you can deny access to all users who do not authenticate. Users who use POP3 or IMAP4 to access this server should authenticate to this server before sending mail.

6. Click the Messages tab to specify message limits for this server. You can also specify how Exchange handles undeliverable mail. In Specify the folllowing message information, you can select options

and enter appropriate values. Select the Limit message size to (KB) check box to limit the

maximum message size. Entering a small value for this option prevents users from sending large documents. However, if you do not limit the maximum message size at all, it can affect performance. It is recommended that you set the maximum message size that is appropriate for your organization.Note Documents expand in size approximately 33 percent when sent outside the routing group or organization. For example, if you want to send documents up to 3 MB in size, set the maximum message size to 4,096 KB.

Select the Limit session size to (KB) check box, and enter a value larger than the maximum message size. Sending a message requires network traffic greater than the size of the message.

Select the Limit number of messages per connection to check box to configure the system to drop the connection after it reaches the specified number of messages. This default setting optimizes message flow in most messaging topologies. You should also understand that selecting this option can lead to a slight performance degradation if your system receives many messages from a single source.

Select the Limit number of recipients per message to check box to have Exchange return the excess recipients to the sender with a non-delivery report (NDR) for messages that exceed the maximum number of recipients. Selecting this check box allows you to keep users from sending an e-mail message to an excessive amount of recipients. Keep the default limit of 64,000 recipients.

In Send a copy of Non-Delivery Reports to, type the SMTP address of the Exchange administrator who you want to receive copies of NDRs. You can use the NDRs to help you diagnose user problems. For


information about examining NDRs, see Q284204 "XCON: Delivery Status Notifications in Exchange 2000 Server" in the Microsoft Knowledge Base. Note NDRs often occur because users type the wrong e-mail address. You may want to disable this feature until you experience problems and need to investigate NDRs.

In Badmail directory, you can modify the location of the messages that are misrouted and cannot be delivered. It is recommended that you keep the default location. Caution Moving the Badmail directory to a disk separate from the queuing directory may degrade performance and make tracking bad messages difficult.

In Forward all mail with unresolved recipients to host, you can specify an alternate host to deliver undeliverable messages if you are sharing a namespace. Sharing a namespace means that there are mail recipients with your domain name that do not belong to the Exchange organization. For example, [email protected] resides in the Exchange organization, and [email protected] resides outside the Exchange organization. In this example, users in [email protected] can send mail to users in [email protected], and Exchange forwards the message on to the alternate host specified.

7. Click the Delivery tab. On this tab you can specify outbound settings such as retry timers, outbound security and connection limits, and other advanced options. In Outbound and Local you can modify the time in minutes for first,

second, third, and subsequent retry attempts at sending a message by entering the appropriate values for your organization.Note Setting the retry intervals too low may degrade performance, particularly when your Internet connection is down or the smart host specified is unavailable. For information about specifying a smart host, see the description of Advanced Delivery options described later in this section. To set Delay notification and Expiration timeout for outbound or

local messages, type the values, and then select the time Minutes, Hours, or Days. It is recommended that you use the default settings.Note Systems on the Internet may have different values for delay notification and expiration timeout. The values entered here refer to messages queued on this server.

Click Outbound Security to configure the authentication the server will use with remote servers. Remote servers on the Internet will not expect your server to

authenticate, so, for most systems, you should click Anonymous access.

If you are connecting to a smart host (as explained under Advanced Delivery options later in this section), it may require you to



authenticate. Check with the owner of the smart host or your ISP to see what is required.

Click Outbound connections to configure connection limits, timeout values, and the TCP port that the server will use with remote servers. Depending on your hardware, you may select the Limit number of

connections to check box to limit connections to other servers and reduce traffic. You may also select the Limit number of connections per domain check box. After you select the check boxes, enter the appropriate vaules for your organization.

Depending on your bandwidth and connection quality, you may want to change the Time-out (minutes) value.Note Reducing the number of outbound connections and increasing the time-out period may cause all your outbound connections to wait for responses from remote servers. With such settings, e-mail remains in the queue for a longer period of time (potentially causing a delay in e-mail delivery), but network traffic is kept to a minimum.

Remote servers on the Internet expect your server to connect to them on TCP port 25. Changing the TCP port is not recommended.

Click Advanced to configure special delivery options. Be aware of the consequences before you change values in the Advanced Delivery dialog box. Changing the value in Maximum hop count limits the number of

servers the message can traverse before being deemed undeliverable. Messages that enter the system with more than the maximum hop count result in non-delivery.Note Systems on the Internet may have different maximum hop counts.

Use the Masquerade domain text box to type an alternate domain for other SMTP servers to use when sending NDRs. NDRs will be returned to the alternate domain specified, instead of the domain from which the e-mail message originated. This setting modifies the domain address as specified in the envelope of all e-mail messages sent from this server running Exchange. Setting a masquerade domain does not change the sender's address as displayed in the From line of the recieving client.Caution Unless users are configured correctly, setting a masquerade domain can cause replies to mail sent from this system to fail.

If you change the Fully-qualified domain name, the name that is presented to remote servers changes. Generally, this setting should be the FQDN of the computer or the mail domain of the organization.Note Some remote servers on the Internet “reverse resolve” the FQDN by verifying that the name given matches the IP address from which it is connected. Check with your DNS administrator that you have reverse DNS lookup records for this server’s IP address corresponding to the FQDN you enter here.


Setting the Smart host at the virtual server level, rather than the SMTP connector level, can cause problems. Keep the following restrictions in mind when you configure the smart host at the virtual server level. Note For more information about using a smart host, see the "Configure a smart host" topic in the Exchange online documentation.

If your Exchange organization contains more than one computer running Exchange, it is recommended that you do not type any data in the Smart host text box, because mail flow between servers may not work.

If an IP address is listed in Smart host, it should be enclosed in square brackets (for example, [10.0.0.1]).

If an IP address is listed in Smart host, verify that it does not match the IP address of this server running Exchange.

If a name is listed in Smart host, it should be a FQDN. For example, Server Name is not a FQDN; however, servername.contoso.com is a FQDN.

If a name is listed in Smart host, it should not be the FQDN of this server.

If you do not have a smart host within your network, check with your ISP to find out what IP address or FQDN you should enter here.

If you do enter a smart host, select the Attempt direct delivery before sending to smart host check box. Selecting this option may help reduce queuing on this server.

If you select the Perform reverse DNS lookup on incoming messages check box, performance may degrade because each incoming connection causes a DNS query. You usually need to select this check box only to assist in troubleshooting looping messages or determining message paths.

To Configure external DNS Servers, click Configure. Configuring external DNS servers allows you to have different servers for resolving names for Windows 2000 and mail delivery. Note If you have external DNS servers for resolving names, and mail delivery is slow or nonexistent, it is recommended that you use the default DNS servers listed in your network connection in Windows 2000.

Step 4: Verify Address Spaces and Delivery Options on SMTP ConnectorsEnsuring that your SMTP connectors are properly configured can prevent message flow problems. If connectors are configured in the routing group, there is one SMTP connector for each routing group.To verify SMTP connector settings


1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.

2. Browse to Connectors by doing one of the following: If you do not have routing groups defined:

Double-click Administrative Groups, double-click <Administrative Group Name>, and then double-click Connectors.

If you have routing groups defined: Double-click Administrative Groups, double-click <Administrative Group Name>, double-click Routing Groups, double-click <Routing Group Name>, and then double-click Connectors.

3. Right-click an SMTP connector, and then click Properties.4. Click the General tab. On this tab, verify the following mail delivery options:

If Use DNS to route to each address space on this connector is selected, verify the following: You can successfully resolve DNS names on the Internet using

NSLOOKUP. On the server running Exchange that is a bridgehead for the connector, do the following:1. At a command prompt, type NSLOOKUP, and then press Enter.2. Type Set Type=MX, and then press Enter.3. Type <Domain Name> (where Domain Name is the name of

your domain), and then press Enter. The mail exchange (MX) record for the domain you entered should be returned. If it is not, DNS is not properly configured. See the "Verify DNS Settings" section later in this document.

If you are using an external DNS server for resolving names and this server is configured at the SMTP virtual server level (that is, using a different DNS server than the one specified on your network connection), test resolving names on the Internet using these servers. Caution As of the publication date for this document, mail flow problems are known to occur when you use external DNS servers for resolving names. If you are using external DNS servers, and if your e-mail delivery is slow or non-existent, it is recommended that you use the Windows 2000 DNS Server service and follow the considerations in the "Step 5: Verify DNS Settings" section later in this document.

If Forward all mail through this connector to the following smart hosts is selected, verify that the following information appears below that option: If an IP address is listed, it should be enclosed in square brackets (for

example, [10.0.0.1]). If an IP address is listed, it should not match the IP address of this

server.


If a name is specified, it should be a FQDN. For example, Server Name is not a FQDN; however, servername.contoso.com is a FQDN.

If a name is specified, it should not be the FQDN of this server. If you do not have a smart host within your network, check with your

ISP to find out what IP address or FQDN you should enter here.5. Click the Address Space tab. On this tab you can specify groupings of

addresses for this connector to manage. Verify the following: Under Create, modify, or remove an address space, verify that at

least one SMTP connector in the organization is set to SMTP for the Type and * for the Address. The * represents all addresses.

Verify that your “inbound” domains are not listed. Your inbound domains are listed in your recipient policies (see "Ensure Recipient Policy Settings Are Correct" earlier in this document). If some or all of your inbound domains are listed, you may receive NDRs indicating a mail loop (these NDRs may have the diagnostic code 5.3.5). Specifying domains on the Address Space tab allows you to configure these domains as routable domains.

Select the Allow messages to be relayed to these domains check box if you want mail to be relayed (routed) through your system to the domains you specified. If clients access this server running Exchange 2000 through POP3 or IMAP4, in most cases, you should select this option. If this option is not selected, relaying may be denied.

For more information, see Q265293 "XFOR: How to Configure the SMTP Connector in Exchange 2000" in the Microsoft Knowledge Base.

Step 5: Verify DNS SettingsA complete analysis and discussion of DNS is beyond the scope of this paper; however, a brief discussion of items to consider when installing and using Exchange is warranted.The DNS server Exchange uses should use the DNS Server service in Windows 2000.

Note Using the DNS Server service in Windows 2000 is not strictly required, but is highly recommended. There are other DNS server software suites, but the DNS server service most tested is the DNS Server service in Windows 2000.

The following guidelines apply to the DNS Server service in Windows 2000.

Settings on the Server Running Exchange

The server running Exchange should typically specify a local DNS server—meaning, it should "point" to a DNS server in its own domain. You specify the DNS server that the servers running Exchange use in Internet Protocol (TCP/IP) Properties. To access Internet Protocol (TCP/IP) Properties for a server



1. Click Start, point to Settings, and then click Network and Dial-up Connections.

2. Double-click Local Area Connection, and then click Properties.3. In Components checked are used by this connection, double-click

Internet Protocol (TCP/IP).The server running Exchange should point to the primary DNS server for your domain. If you have multiple local DNS servers, you may configure Exchange to point to any of them. However, it is recommended that Exchange point to the primary DNS server for that domain.

Settings on the DNS Server

Configure the DNS server according to the following guidelines. For more information about guidelines for configuring DNS, see the Microsoft Knowledge Base article referenced at the end of this section. Ensure that the DNS server points to its own IP address. To confirm this

setting, access the Internet Protocol (TCP/IP) Properties for the DNS server. See the "To access Internet Protocol (TCP/IP) Properties for a server" procedure earlier in this document.

The DNS server should contain Forward Lookup Zones for each of the domains being hosted. You configure these settings on the General tab in the <Forward Lookup Zone Name> Properties dialog box in the DNS console. For each Forward Lookup Zone:

Allow dynamic updates should be set to Yes. Type should preferably be set to Active Directory Integrated.

The DNS server should contain Reverse Lookup Zones for each IP subnet range being hosted. These settings are configured on the General tab in the <Reverse Lookup Zone Name> Properties dialog box in the DNS console. For each Reverse Lookup Zone:

Allow dynamic updates should be set to Yes. Type should preferably be set to Active Directory Integrated.

You should configure your DNS server to include forwarders to external (Internet) DNS servers. This setting allows your DNS server to receive queries for external names, forward the query to the remote server, and deliver the response to the requestor. To configure this setting, open the DNS console, right-click your server running Exchange, click Properties, click the Forwarders tab, and then configure forwarders to external DNS servers.

Note If Enable Forwarders on the Forwarders tab is unavailable, the DNS server was configured as a root DNS server. To configure forwarders, you must remove the "." (dot) zone, restart the DNS console, and then configure your forwarders.

For more information about DNS, Windows 2000, and Active Directory, see Q298448 "Windows 2000 DNS and Active Directory Information and Technical Resources" in the Microsoft Knowledge Base.



Step 6: Verify SMTP Port SettingsWhen a server running Exchange communicates over SMTP, it requires access to port 25. When SMTP is properly configured, Exchange provides extended SMTP verbs to allow proper communication. These verbs are controlled in the metabase and in Exchange event sinks.You can perform a Telnet test to determine whether or not the proper extended Exchange verbs are loaded. To perform this test, telnet to port 25 of the IP address of your server running Exchange. For example, type the following at a command prompt:

telnet 127.0.0.1 25Table 1 displays the verbs you will receive if SMTP is loaded properly in Exchange. The SMTP listener of the server running Exchange sends these verbs. If SMTP is not properly configured, you will see only the verbs listed in Table 2. Table 1 SMTP extended verbs if Exchange event sinks are loaded properly

Banner (from server): 220 server.contoso.com Company ESMTP Mail Service, Version 5.0.2195.1600 ready at Fri, 8 Jun 2001 15:00:00 -0400

EHLO (user typed): EHLO 10.0.0.1

Response (from Server): 250-server.contoso.com Hello [10.0.0.1]

250-TURN

250-ATRN

250-SIZE

250-ETRN

250-PIPELINING

250-DSN

250-ENHANCEDSTATUSCODES

250-8bitmime

250-BINARYMIME

250-CHUNKING

250-VRFY

* 250-X-EXPS GSSAPI NTLM LOGIN

* 250-X-EXPS=LOGIN

250-AUTH GSSAPI NTLM LOGIN

250-AUTH=LOGIN

* 250-XEXCH50

* 250-X-LINK2STATE


250 OK

* You should see these extended verbs.When Exchange SMTP is not loaded properly, Exchange event sinks are bound in the metabase, and do not appear. Table 2 displays the verbs you will receive if Exchange SMTP is not loaded properly. The verbs you see with an improperly loaded Exchange SMTP are the same as the verbs you would see if you had never installed Exchange. Table 2 SMTP extended verbs if Exchange 2000 sinks are not loaded

250-servername.contoso.com Hello [127.0.0.1]

250-AUTH GSSAPI NTLM LOGIN

250-AUTH=LOGIN

250-TURN

250-ATRN

250-SIZE 2097152

250-ETRN

250-PIPELINING

250-DSN

250-ENHANCEDSTATUSCODES

250-8bitmime

250-BINARYMIME

250-CHUNKING

250-VRFY

250 OK

If you receive only the SMTP verbs listed in Table 2, the SMTP service for Windows 2000 is installed but SMTP in Exchange is not loaded properly. Note that all verbs starting with “X” (“X” denotes Exchange) are missing. If this is the case, you must properly load Exchange SMTP by doing the following:To properly load Exchange SMTP1. Reapply Windows 2000 Server Service Pack 1 (SP1).2. Reinstall Exchange. Reinstalling Exchange replaces any missing files without

affecting the settings on the server running Exchange.3. Reapply any Exchange service packs and any other Exchange-related

program updates (for example, any Exchange updates available from the Microsoft Download Center).


Step 7: Use Message TrackingYou can use Message Tracking Center in Exchange to log information about messages sent over your messaging system. Message Tracking Center logs information about the sender, the mail message, and the message recipients. Specifically, you can determine statistics such as the time the message was sent or received, the message size and priority, and the list of message recipients. You can also log the subject line of e-mail messages. Message Tracking Center searches for all types of messages, including system messages, public folder messages, and e-mail messages.You must enable Message Tracking Center on each server for which you want to track messages. When enabled, all messages routed through a server are added to the message tracking logs. To enable Message Tracking Center on a server1. Click Start, point to Programs, point to Microsoft Exchange, and then click

System Manager.2. In the console tree, double-click Servers, right-click the server on which you

want to enable message tracking, and then click Properties.3. On the General tab, select the Enable message tracking check box.4. To record the subject of any message sent to, from, or through the server,

select the Enable subject logging and display check box.Note Enabling subject logging causes some performance degradation.

5. In Log file maintenance, you can prevent the removal of log files or modify the length of time the log files are kept. The default period that tracking logs are kept is 7 days.Note On servers that process large quantities of mail, the tracking logs grow quickly. Ensure that you have adequate disk space for the log files and for other services or applications that use this disk.

6. Click OK or Apply. You do not need to restart services for this change to take effect.

For more information about how to use Message Tracking Center, see Q262162 “XADM: Using the Message Tracking Center to Track a Message” in the Microsoft Knowledge Base.

Step 8: Use Event ViewerIn Event Viewer, Application Log contains errors, warnings, and information events related to the operation of Exchange and other applications on the system. Carefully reviewing the data contained in Application Log can help you identify the cause of message flow issues you may encounter.

Note Because Exchange uses features in Windows 2000, viewing System Log on a regular basis is also recommended. If the services and features of Windows 2000 that Exchange uses fail, they may log events in System Log.

To use Event Viewer to view Application Log



1. Click Start, point to Programs, point to Administrative Tools, and then click Event Viewer.

2. Click Application Log.3. To sort the log alphabetically and quickly locate an entry for an Exchange

service, click Source. 4. Double-click a log entry to open an event’s property page.5. To filter the log to list entries for a specific type of Exchange-related event,

from the View menu, click Filter. In Event source, select an Exchange-related event source. For example: MSExchangeTransport Select this event source to view events

recorded when SMTP is used to route messages. IMAP4Svc Select this event source to view events related to the service

that allows users to access mailboxes and public folders through IMAP4. MSExchangeAL Select this event source to view events related to the

service that addresses e-mail through address lists. MSExchangeIS Select this event source to view events related to the

service that allows access to the Information Store service. MSExchangeMTA Select this event source to view events related to the

service that allows X.400 connectors to use the message transfer agent (MTA).

MSExchangeSA Select this event source to view events recorded when Exchange uses Active Directory to store and share directory information.

MSExchangeSRS Select this event source to view events recorded whenever Site Replication Service is used to replicate computers running Exchange 2000 with computers running Microsoft Exchange Server version 5.5.

POP3Svc Select this event source to view events recorded whenever POP3 is used to access e-mail.

6. In Category, select a specific set of events or leave the default setting, All, to view all events for that event source.

7. Click OK.

Configuring Diagnostic Logging

To help you determine the root of a transport issue, view events that relate to MSExchangeTransport. As soon as you start to experience problems with Exchange message flow, increase the logging levels relating to MSExchangeTransport. Logging levels control the amount of data logged in Application Log. The more events logged, the more transport-related events you can view in Application log, and the better your chance is for determining the cause of the message flow problem. To modify logging settings for MSExchangeTransport


1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.

2. Double-click Servers.3. Right-click <Server Name>, and then click Properties.4. Click the Diagnostics Logging tab.5. Under Services, click MSExchangeTransport.6. Under Categories, click the category for which you want to configure the

logging level.7. Under Logging level, click None, Minimum, Medium, or Maximum.Caution If you increase the logging levels for Exchange services, you will experience some performance degradation. It is recommended that you increase the size of Application Log to contain all the data produced. If you do not increase the size of the Application Log, you will receive frequent reminders that the Application Log is full.

Additional ResourcesFor more information about how to optimize and troubleshoot Exchange, see Microsoft Exchange 2000 Server Resource Kit. The resource kit provides various details regarding performance monitoring, Event Viewer, and other troubleshooting tools.

The resource kit is available online at: http://www.microsoft.com/exchange/techinfo/reskit/default.asp

You can also review the following Microsoft Knowledge Base articles: Q288175 XCON: Recipient Policy Cannot Match Fully Qualified Domain Name

of Any Server in Org Q140933 XFOR: SMTP Proxy Address Generated Incorrectly Q262162 XADM: Using the Message Tracking Center to Track a Message Q265293 XFOR: How to Configure the SMTP Connector in Exchange 2000 Q276388 XIMS: How to Configure Exchange 2000 Behind Proxy Server 2.0 Q260973 XCON: Setting Up SMTP Domains for Inbound and Relay E-Mail in

Exchange 2000 Server Q284204 XCON: Delivery Status Notifications in Exchange 2000 Server Q27883 8 XCON: Cannot Send Mail to SMTP Domain That Is the Same as the

Local Exchange Organization Domain Q275596 XADM: MAPI Messages Stack Up in Send Queue to the Host

Specified in Forward Unresolved Recipients Q280794 XIMS: Message Cannot Be Sent to Domains with MX Record

Pointing to CNAME Record







http://support.microsoft.com/support/kb/articles/Q265/2/93.ASP?LN=EN-US&SD=gn&FR=0&qry=%26%25




http://www.microsoft.com/exchange/techinfo/reskit/default.asp


Q298448 Windows 2000 DNS and Active Directory Information and Technical Resources

For more information: http://www.microsoft.com/exchange/

Did this paper help you? Please give us your feedback. On a scale of 1 (poor) to 5 (excellent), how would you rate this paper?

mailto:[email protected]?subject=Feedback: Troubleshooting Mail Flow Issues in Microsoft Exchange 2000 -- A Step-by-Step Approach

mailto:[email protected]?subject=Feedback:%20Troubleshooting%20Mail%20Flow%20Issues%20in%20Microsoft%20Exchange%202000%20--%20A%20Step-by-Step%20Approach

mailto:[email protected]?subject=Feedback:%20Troubleshooting%20Mail%20Flow%20Issues%20in%20Microsoft%20Exchange%202000%20--%20A%20Step-by-Step%20Approach

http://www.microsoft.com/exchange/



The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.

This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THE INFORMATION IN THIS DOCUMENT.

Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, email address, logo, person, place or event is intended or should be inferred.

2001 Microsoft Corporation. All rights reserved.

Microsoft, Active Directory, Outlook, and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Date post:	09-Mar-2018
Category:	Documents
Upload:	phungliem
View:	222 times
Download:	0 times