کد:
http://itprosecure.com/blogs/exchange_2007_administration/archive/2007/08/20/troubleshooting-smtp-mailflow-and-smart-host-connectivity-in-exchange-2007.aspx

Once you gain placement of several Ex2k7 Servers by Role and connect them to the Internet, either using a Smart Host or acting as 'Authoritative' for an SMTP Namespace (such as @itprosecure.com) it's imperative to understand how to Troubleshoot SMTP Mailflow (between Hub Transport and Edge Transport for example) and Smart Host Connectivity (to Message Hygiene Services such as Microsoft Exchange Hosted Services, MessageLabs and Postini). The following articles should be of value:


How to Configure Connectivity Logging

"Connectivity logging records the connection activity of the outgoing message delivery queues that exist on computers that have the Hub Transport server role or Edge Transport server role installed. The purpose of the connectivity log is not to track the transmission of individual e-mail messages. The connectivity log tracks the connection activity from the sending queue to the destination Mailbox server, smart host, or domain."
How to Configure Protocol Logging
"Protocol logging records the Simple Mail Transfer Protocol (SMTP) conversations that occur between e-mail servers as part of message delivery. These SMTP conversations occur on Send connectors and Receive connectors that are configured on Exchange 2007 servers that have the Hub Transport server role or the Edge Transport server role installed. You can use protocol logging to diagnose mail flow problems."
Here's an example of configuring Connectivity Logging:

Here the Windows PowerShell (or Exchange Management Shell) is invoked.

I start by validating synchronization between the Hub Transport Server Role (Domain-Joined Ex2k7 Server) and the Edge Transport Server Role (Workgroup Mode with 2 NIC Interfaces) using the 'Test-EdgeSynchronization' Commandlet.

The Connectivity Path is modified from its default location of (C:\Program Files\Microsoft\Exchange\....) to my preferred location of C:\Documents and Settings\Administrator.CORP\Desktop\Connectivity_L ogs.

The same Exchange Management Shell Commandlet of 'Set-TransportServer' is used with the -ConnectivityLogEnabled $true parameters. Connectivity Logging should be enabled if the folder specified in this parameter includes the appropriate permissions for the Network Service User Context.

We observe the first Connectivity Log in our new destination folder (after changing the Permissions as specified in the document above). Additionally, I moved to a separate WinXPSP2/OL2k7 Client and sent an e-mail to an external e-mail recipient (user@domain.com) who was not part of my Lab Environment (which is user@itpslabmail.com) to ensure SMTP Mail Transport between the Hub Server Role and the Edge Server Role.

Our Connectivity Logs indicate connectivity between the Server Roles with detail appropriate to further troubleshoot connectivity issues.

The final step (once troubleshooting is completed) and an intended solution is reached is to 'turn off' Connectivity Logging using the -ConnectivityEnabled $false parameter for the 'Set-TransportServer' Commandlet



موضوعات مشابه: