Module 5

Managing Message Transport

Module Overview

• Overview of Message Transport

• Configuring Message Transport

Lesson 1: Overview of Message Transport

• Discussion: Overview of Message Flow

• Components of Message Transport

• How Are Messages Routed in an Exchange Server Organization?

• How Are Messages Routed Between Active Directory Sites?

• Options for Modifying the Default Message Flow

• Tools for Troubleshooting SMTP Message Delivery

• Demonstration: How to Troubleshoot SMTP Message Delivery

Discussion: Overview of Message Flow

• What is SMTP?

• What are the various message-flow scenarios?

• What type of message-flow scenarios do most organizations implement?

Components of Message Transport

ComponentDescription

Submission queue Stores all messages on disk until processed

Store driver Retrieves messages from sender’s Outbox

Microsoft Exchange Mail Submission service

Notifies a Hub Transport server in the local Active Directory site when a message is available for retrieval from a sender’s Outbox

CategorizerProcesses one message at a time from the Submission queue

Pickup directory Submits messages to the Submission Queue

How Are Messages Routed in an Exchange Server Organization?

InternetInternet

Hub Transport server

Hub Transport server

Mailbox serverMailbox server

Outlook client

Outlook client

Client Access server

Client Access server

332211

6655

44

How Are Messages Routed Between Active Directory Sites?

2020

2020

10101010

Default message

flow

Default message

flow

Source Site

Source Site

Destination Site

Destination Site

1010

Delayed fan-outDelayed fan-out

Queue at the point of failure

Queue at the point of failure

2020

2020

10101010

Default message

flow

Default message

flow

Source Site

Source Site

Destination Site

Destination Site

1010

Options for Modifying the Default Message Flow

To modify the default message flow, you can:

Configure hub sites to add additional hops to the message delivery

Configure Exchange-specific routing costs to override the IP site link costs

Configure expansion servers for distribution groups

Tools for Troubleshooting SMTP Message Delivery

Tool Description

Exchange Server Best Practices Analyzer

Use to check the configuration and health of the Exchange topology

Exchange Mail Flow Troubleshooter

Use to troubleshoot common mail-flow problems

Queue Viewer Use to view and manage undelivered messages

Message Tracking & Tracking Log Explorer

Use to confirm message delivery

Routing Log Viewer Use to view the message routing topology

Protocol Logging Use to provide detailed protocol-level information

Telnet Use to check if the SMTP port responds or to directly send a SMTP mail to a connector

Demonstration: How to Troubleshoot SMTP Message Delivery

In this demonstration, you will see how to:

• Use Telnet to check if Exchange Server responds correctly

• Use Queue Viewer to troubleshoot SMTP message delivery

Lesson 2: Configuring Message Transport

• Process for Configuring Hub Transport Servers

• Demonstration: How to Configure Hub Transport Servers

• Options for Configuring Message Transport

• What Are Accepted Domains?

• What Are Remote Domains?

• Demonstration: How to Configure Accepted and Remote Domains

• What Is an SMTP Connector?

• Demonstration: How to Configure SMTP Send and Receive Connectors

• What Is Back Pressure?

Process for Configuring Hub Transport Servers

To configure a Hub Transport server:

Configure a postmaster mailbox

Configure authoritative domains and e-mail address policies

Configure server-specific settings

Configure Internet message flow

Configure messaging policies

Configure administrative permissions

11

22

33

44

55

66

Demonstration: How to Configure Hub Transport Servers

In this demonstration, you will review:

• Options at the global and server level

• Default configuration

• Options for changing the default configuration for Hub Transport servers

Options for Configuring Message Transport

• Moderated transport

• Enhanced disclaimers

• Anti-spam and antivirus protection

• Rights protection using transport protection rules

• Transport rules

• Journaling

What Are Accepted Domains?

Accepted domains can be:

• Internal relay domains

• Authoritative domains

Accepted domains define SMTP domain names for which the Exchange server will accept e-mailAccepted domains define SMTP domain names for which the Exchange server will accept e-mail

• External relay domains

What Are Remote Domains?

Properties of remote domains are:

• Out-of-office message delivery

Remote domains define SMTP domains that are external to your Exchange organization Remote domains define SMTP domains that are external to your Exchange organization

• Message format options including acceptable character sets

Demonstration: How to Configure Accepted and Remote Domains

In this demonstration, you will review:

• The default accepted domain configuration

• How to configure accepted domains

• How to configure one remote domain

What Is an SMTP Connector?

SMTP Receive Connectors:

• Accept SMTP messages from other hosts

• Must use a unique combination of port number, listening IP address, and accepted remote IP addresses

SMTP connectors are Exchange Server components that support one-way SMTP connectionsSMTP connectors are Exchange Server components that support one-way SMTP connections

SMTP Send Connectors:

• Send SMTP messages to other servers

• Are required to send e-mail to any SMTP server

Demonstration: How to Configure SMTP Send and Receive Connectors

In this demonstration, you will see how to:

• Create and configure a SMTP Send connector

• Create and configure a SMTP Receive connector

What Is Back Pressure?

Resource Utilization Level

Description

Normal The resource is not overused. The server accepts new connections and messages

Medium The resource is slightly overused. Back pressure is applied to the server in a limited manner. Mail from senders in the authoritative domain can flow. However, the server rejects new connections and messages from other sources

High The resource is severely overused. Full back pressure is applied. All message flow stops, and the server rejects all new connections and messages

Back pressure is a system-resource monitoring feature that you can use to:

• Monitor system resources such as available hard disk, drive space, and memory

• Restrict new connections and messages if a system resource exceeds a specified level

• Prevent the server from being completely overwhelmed

Lab: Managing Message Transport

• Exercise 1: Configuring Internet Message Transport

• Exercise 2: Troubleshooting Message Transport

• Exercise 3: Troubleshooting Internet Message Delivery

Logon information

Estimated time: 60 minutes

Virtual machines10135A-VAN-DC1, 10135A-VAN-EX1, 10135A-VAN-EX2

User name Administrator

Password Pa$$w0rd

Lab Scenario

You are a messaging administrator in A. Datum Corporation, which is a large multinational organization that includes offices in London, Tokyo, and Vancouver, which is its headquarters. Your organization has deployed Exchange Server 2010 in two of its sites. However, all Internet messages should flow through the main site in Vancouver. As part of your job responsibilities, you need to set up the message transport to and from the Internet and also ensure that the message flow works within and between the various sites.

Lab Review

• What would you need to configure to enable outbound Internet e-mail from each of Adatum‘s location?

• A user calls and reports that she sent a message to a user in another company two hours ago, and the message has not arrived. How would you troubleshoot this?

• After A. Datum. bought some new locations, you want to make sure that all e-mail messages are passed through the main site in Vancouver. How would you do that?

Module Review and Takeaways

• Common Issues and Troubleshooting Tips