22
Module 5 Managing Message Transport

10135 b 05

Embed Size (px)

DESCRIPTION

 

Citation preview

Page 1: 10135 b 05

Module 5

Managing Message Transport

Page 2: 10135 b 05

Module Overview

• Overview of Message Transport

• Configuring Message Transport

Page 3: 10135 b 05

Lesson 1: Overview of Message Transport

• 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

Page 4: 10135 b 05

Components of Message Transport

Submission queue

Submission queue

Exchange Mail Submission service

Exchange Mail Submission service

SMTP Receive connecter

SMTP Receive connecter

Pickup and Replay directories

Pickup and Replay directories

AgentdeliveryAgent

delivery

Remote delivery queue

Remote delivery queue

Mailbox delivery queue

Mailbox delivery queue

CategorizerCategorizer

Store driverStore driver

SMTP Send connector

SMTP Send connector

User mailbox

User mailbox

Hub Transport server

Mailbox serverDeliver to Inbox

Submit from Outbox

Page 5: 10135 b 05

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

Page 6: 10135 b 05

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 siteDestination site

1010

Page 7: 10135 b 05

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

Page 8: 10135 b 05

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

TestExchange Connectivity Website

Use to test connectivity to Exchange services from outside

Page 9: 10135 b 05

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

Page 10: 10135 b 05

Lesson 2: Configuring Message Transport

• Process for Configuring Hub Transport Servers

• Demonstration: How to Configure Hub Transport Servers

• 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?

Page 11: 10135 b 05

Process for Configuring Hub Transport Servers

To configure a Hub Transport server:

Configure a postmaster mailbox

Configure authoritative domains and email address policies

Configure server-specific settings

Configure Internet message flow

Configure messaging policies

Configure administrative permissions

11

22

33

44

55

66

Page 12: 10135 b 05

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

Page 13: 10135 b 05

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 emailAccepted domains define SMTP domain names for which the Exchange server will accept email

• External relay domains

Page 14: 10135 b 05

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

Page 15: 10135 b 05

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

Page 16: 10135 b 05

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 email to any SMTP server

Page 17: 10135 b 05

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

Page 18: 10135 b 05

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

Page 19: 10135 b 05

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

Page 20: 10135 b 05

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.

Page 21: 10135 b 05

Lab Review

• What would you need to configure to enable outbound Internet email 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 email messages are passed through the main site in Vancouver. How would you do that?

Page 22: 10135 b 05

Module Review and Takeaways

• Common Issues Related to Managing Message Transport