Overview of Exchange 2013 Architecture Transport components shipping with Exchange 2013 Mail Routing Scenarios Transport High Availability SMTP Client

Khushru IraniProgram ManagerMicrosoft

ARC.304 Exchange Server 2013 Transport Architecture

ARC304

AgendaOverview of Exchange 2013 ArchitectureTransport components shipping with Exchange 2013Mail Routing ScenariosTransport High AvailabilitySMTP Client Submission

Exchange 2013 Architecture Overview

Exchange 2010 vs. 2013 Arch Overview

DAG

MBX

CAS HUB UM

SMTPEAS VOiP

Protocols; API;

BizLogic

Auth; Proxy; Redirect

Exchange 2010

Exchange 2010 vs. 2013 Arch Overview

DAG

MBX

CAS HUB UM

SMTPEAS VOiP

Protocols; API;

BizLogic


DAG

MBX

HUB*

UM

SMTPEAS VOiP

Protocols; API;

BizLogic


Prot*

MBXServer

ServerCAS

Exchange 2010 Exchange 2013

* The names are not exactly ‘Hub’ and ‘Prot’; this is for illustration purposes only

Mail Delivery Overview

DAG

MBX

HUB HUB

SMTP

Internet

Site BSite A

Exchange 2010

Sit

e B

ou

nd

ary


DAG

MBX

HUB HUB

SMTP

Internet

Site BMAPI

Site A

Exchange 2010

Sit

e B

ou

nd

ary


DAG

MBX

HUB HUB

Internet

Site B

SMTP

Site A

Exchange 2010

Sit

e B

ou

nd

ary


DAG

MBX

HUB HUB

Internet

Site B

SMTP

SMTP

Site A

Exchange 2010

Sit

e B

ou

nd

ary


DAG

MBX

HUB HUB

Internet

Site BMAPI

SMTP

SMTP

Site A

Exchange 2010

Sit

e B

ou

nd

ary


DAG

MBX

HUB HUB

SMTP

Internet

Site BMAPI

SMTP

SMTP

Site A

Exchange 2010

Sit

e B

ou

nd

ary


DAG

MBX

HUB HUB

SMTP

DAG Transport

SMTP

CAS

Internet

Site BMAPI

SMTP

SMTP

Site A

Internet

Transport

MBX

CASFrontend Frontend


Site A Site B

Sit

e B

ou

nd

ary

Sit

e B

ou

nd

ary

Mailbox Transport

Mailbox Transport


DAG

MBX

HUB HUB

SMTP

DAG Transport

SMTP

CAS

Internet

Site BMAPI

SMTP

SMTP

Site A

Internet

Transport

MBX



Site A Site B SMTP

Sit

e B

ou

nd

ary

Sit

e B

ou

nd

ary

Mailbox Transport

Mailbox Transport


DAG

MBX

HUB HUB

SMTP

DAG Transport

SMTP

CAS

Internet

Site BMAPI

SMTP

SMTP

Site A

Internet

Transport

MBX



Site A Site B SMTP

SMTP

MAPI

Sit

e B

ou

nd

ary

Sit

e B

ou

nd

ary

Mailbox Transport

Mailbox Transport


DAG

MBX

HUB HUB

SMTP

DAG Transport

CAS

Internet

Site BMAPI

SMTP

SMTP

Site A

Internet

Transport

MBX


SMTP


Site A Site B

Sit

e B

ou

nd

ary

Sit

e B

ou

nd

ary

Mailbox Transport

Mailbox Transport


DAG

MBX

HUB HUB

SMTP

DAG Transport

CAS

Internet

Site BMAPI

SMTP

SMTP

Site A

Internet

Transport

MBX


SMTP


Site A Site BSMTP

Sit

e B

ou

nd

ary

Sit

e B

ou

nd

ary

Mailbox Transport

Mailbox Transport


DAG

MBX

HUB HUB

SMTP

DAG Transport

CAS

Internet

Site BMAPI

SMTP

SMTP

Site A

Internet

Transport

MBX


SMTP


Site A Site BSMTP

SMTP

MAPI

Sit

e B

ou

nd

ary

Sit

e B

ou

nd

ary

Mailbox Transport

Mailbox Transport


DAG

MBX

HUB HUB

SMTP

DAG Transport

SMTP

CAS

Internet

Site BMAPI

SMTP

SMTP

Site A

Internet

Transport

MBX


SMTP


Site A Site B SMTPSMTP

SMTP

SMTP

MAPI

Sit

e B

ou

nd

ary

Sit

e B

ou

nd

ary

Mailbox Transport

Mailbox Transport

Mail Submission Overview

DAG

HUB HUB

Internet

Exchange 2010

Notify

MAPIMBX

Sub Sub


DAG

HUB HUB

Internet

MAPI

Exchange 2010

Notify

MAPIMBX

Sub Sub


DAG

HUB HUB

SMTP

Internet

MAPI

Exchange 2010

Notify

MAPIMBX

Sub Sub


DAG Transport

CAS

Internet

Transport

MBX


Exchange 2013

Notify

MAPI

Mailbox Transport

Mailbox Transport

DAG

HUB HUB

SMTP

Internet

MAPI

Exchange 2010

Notify

MAPIMBX

Sub Sub


DAG Transport

CAS

Internet

Transport

MBX


Exchange 2013

MAPI

Mailbox Transport

Mailbox Transport

DAG

HUB HUB

SMTP

Internet

MAPI

Exchange 2010

Notify

MAPIMBX

Sub Sub


DAG Transport

CAS

Internet

Transport

MBX


Exchange 2013

SMTP

MAPI

Mailbox Transport

Mailbox Transport

DAG

HUB HUB

SMTP

Internet

MAPI

Exchange 2010

Notify

MAPIMBX

Sub Sub


DAG Transport

CAS

Internet

Transport

MBX


SMTP

Exchange 2013

SMTP

SMTP

MAPI

Mailbox Transport

Mailbox Transport

DAG

HUB HUB

SMTP

Internet

MAPI

Exchange 2010

Notify

MAPIMBX

Sub Sub

AD

Web browser

Outlook (remote

user)

Mobile phone

Outlook (local user)

ExternalSMTP

servers

Exchange Online

Protection

Enterprise Network

2 Building Blocks

Client Access Server (CAS) Role• Evolution of

E2010 CAS Array• Now includes

SMTP Frontend Transport• Primary function

is to get the client to the right MBX server

Mailbox Server Role• Now includes all

core messaging protocols• Now includes Transport and Mailbox Transport (Delivery & Submission)

Layer

4LB

CAS Array

Exchange 2013 Server Role Architecture

CAS

CAS

CAS

CAS

CAS

DAG2

MBX

MBX

MBX

…

DAG3

MBX

MBX

MBX

…

DAG1

MBX

MBX

MBX

…

Frontend Transport

Mailbox Transport

Transport

AD

Web browser

Outlook (remote

user)

Mobile phone


ExternalSMTP

servers

Exchange Online

Protection

Enterprise Network

1. Email enters the organization

Layer

4LB

CAS Array


CAS

CAS

CAS

CAS

CAS

DAG2

DAG3

DAG1

1

AD

Web browser

Outlook (remote

user)

Mobile phone


ExternalSMTP

servers

Exchange Online

Protection

Enterprise Network

Layer

4LB

CAS Array


CAS

CAS

CAS

CAS

CAS

DAG2

DAG3

DAG1

2


2. Frontend Transport running on CAS server accepts the mail

1

AD

Web browser

Outlook (remote

user)

Mobile phone


ExternalSMTP

servers

Exchange Online

Protection

Enterprise Network

Layer

4LB

CAS Array


CAS

CAS

CAS

CAS

CAS

DAG2

DAG3

DAG1

2

3



3. Frontend Transport determines DAG for this recipient

1

AD

Web browser

Outlook (remote

user)

Mobile phone


ExternalSMTP

servers

Exchange Online

Protection

Enterprise Network

Layer

4LB

CAS Array


CAS

CAS

CAS

CAS

CAS

DAG2

DAG3

DAG1



3. Frontend Transport determines DAG for this recipient

4. CAS sends mail to a MBX server in the recipients DAG [prefers MBX server in its own site]

2

31

MBX

MBX

…4

Transport Components in Exchange 2013

Transport componentsTransport ships 3 major components in Exchange 2013Frontend Transport – Stateless SMTP service on client access roleTransport – Stateful SMTP service on mailbox roleMailbox Transport – Stateless SMTP service on mailbox role

Transport responsibilities (unchanged)

Receive and deliver all inbound mail to the organization Submit and deliver all outbound mail from the organizationPerform all message processing within the pipelineSupport extensibility within pipelineKeep messages redundant until successfully delivered

Frontend Transport

AD

Web browser

Outlook (remote

user)

Mobile phone


ExternalSMTP

servers

Exchange Online

Protection

Enterprise Network

Layer

4LB

CAS Array

CAS

CAS

CAS

CAS

DAG2

MBX

MBX

MBX

…

DAG3

MBX

MBX

MBX

…

DAG1

MBX

MBX

MBX

…

Frontend Transport

2 Building Blocks






core messaging protocols• Now includes

Transport and Mailbox Transport (Delivery & Submission)

Handles inbound and outbound external SMTP traffic

(Does not replace the Edge Transport Server Role)

Handles authenticated client submissions

Functions as a layer 7 proxy and has full access to protocol conversation (inbound)

Will not queue or bifurcate mail locally

All outbound traffic to next hop appears to come from the CAS2013

Listens on TCP25 and TCP587 and TCP717

Frontend Transport

Frontend Transport

SMTP Receive Protocol

Agents

SMTP from MBX 2013

Authenticated

SMTP

SMTP Send

SMTP to MBX 2013

External SMTP

Mailbox Selector

:25

:717

MSExchangeFrontendTransport.exe

:587

AnonymousSMTP

Benefits of Frontend TransportNetwork protection – centralized, load balanced egress/ingress point for the organizationMailbox locator – avoids unnecessary hops by determining the best Mailbox to deliver the messageProvides unified namespace, for authenticated and anonymous mailflow scenariosScales based on number of connections

Transport*

AD

Web browser

Outlook (remote

user)

Mobile phone


ExternalSMTP

servers

Exchange Online

Protection

Enterprise Network

Layer

4LB

CAS Array

CAS

CAS

CAS

CAS

CAS

DAG2

MBX

MBX

…

DAG3

MBX

MBX

…

DAG1

MBX

MBX

…

Transport

Transport

Transport

*previously known as Hub Transport

2 Building Blocks






core messaging protocols• Now includes Transport and Mailbox Transport (Delivery & Submission)

Processes all SMTP mail flow for the organization

Will queue and route messages in and out of the organization

Performs content inspection

Supports extensibility in SMTP and categorizer

Listens on TCP 25 (or TCP2525 when co-located with CAS)

*previously known as Hub Transport

Transport*

Transport

SMTP to MBX-Transport

Delivery

SMTP from MBX-Transport Submission

SMTP from CAS

SMTP to CAS, MBX, HUB

Delivery Agents

*other protocols

Delivery Queue

Delivery Queue

Pickup/Replay

Categorizer

Routing Agents

SMTP Send

SMTP Receive

Protocol Agents

:25 or :2525

:25

Edgetransport.exe

Mail.que

Submission Queue

Transport Pipeline

Categorizer

ResolveRecipients

SMTP Send

SMTP Receive

Protocol Agents

:25 or :2525

:25

Mail.que

Submission Queue

Find Route for Recipient

Content Conversion

& Bifurcation

On Submitted On Resolved

On Routed On Categorized

External Delivery Queue

Internal Delivery Queue

Mailbox Delivery Queue

• All incoming mail is stored in the mail.que database• All mail passes through the various stages of the categorizer • There is exactly one submission queue but multiple delivery

queues (one per destination)• Agents subscribe to various events along the pipeline – Transport

rules agent; Journaling agent; Malware agent; 3rd party agents

Benefits of TransportPerforms all routing decisions for internal and external messagesProvides an extensibility platform for third-party agents to operate within the pipelineAllows messages to be routed in or out through connectors for special handlingProtects messages by making messages highly available on ‘shadow’ servers

Mailbox Transport

AD

Web browser

Outlook (remote

user)

Mobile phone


ExternalSMTP

servers

Exchange Online

Protection

Enterprise Network

Layer

4LB

CAS Array

CAS

CAS

CAS

CAS

CAS

DAG2

MBX

MBX

…

DAG3

MBX

MBX

…

DAG1

MBX

MBX

…

Mailbox Transpor

t

MailboxTranspor

t

Mailbox Transport

2 Building Blocks






core messaging protocols• Now includes

Transport and Mailbox Transport (Delivery & Submission)

Handles mail submission and delivery from/to Store using two separate processes

Does not have persistent storage

Performs MIME to MAPI conversion (and vice versa)

Combines Mailbox Assistant and Store Driver functionality

(Supports all E2010 store driver extensibility events)

Leverages local RPC for delivery to and submission from Store

Does not support any extensibility

Mailbox TransportSMTP from Transport

Mailbox Transport

SMTP SendSMTP

Receive

Submission

Mailbox Assistant

s

MAPI MAPI

Store

SMTP to Transport

Submit Agents

:475

MSExchangeDelivery.exe MSExchangeSubmission.exe

SMTP Send

Deliver Agents

Delivery

SMTP to Transport

Benefits of Mailbox TransportBrings together all transport scenarios that access mailbox store under one componentEliminates the three-party mail submission hand-shakeHelps realize the “every server is an island” vision by ensuring MAPI is not used across the serverSimplifies handling of mailbox DB *over scenarios

AD

Web browser

Outlook (remote

user)

Mobile phone


ExternalSMTP

servers

Exchange Online

Protection

Enterprise Network

Layer

4LB

CAS Array


CAS

CAS

CAS

CAS

CAS

DAG2

MBX

MBX

MBX

…

DAG3

MBX

MBX

MBX

…

DAG1

MBX

MBX

MBX

…

Edge Transport 2013Ships in SP1

Used in perimeter network (non-domain joined) to accept mail

Same feature set as Edge role in 2010

New monitoring framework (like rest of Exchange 2013)

No AV; basic Anti-spam features; No Shadow copy

Client submission still works via CAS


AD

Web browser

Outlook (remote

user)

Mobile phone


ExternalSMTP

servers

Exchange Online

Protection

Enterprise Network

DAG2

MBX

MBX

MBX

…

DAG3

MBX

MBX

MBX

…

DAG1

MBX

MBX

MBX

…

Edge Transport

Layer

4LB

CAS Array

CAS

CAS

CAS

CAS

CAS

Mail routing scenarios

• Scenario 1 – Incoming mail on a multi-role server• Scenario 2 – Incoming mail to two recipients• Scenario 3 – Originating mail to Internet• Scenario 4 – Originating mail to multiple recipients

Mail routing scenarios

• CAS server will attempt to anchor on a recipient

• CAS server will lookup recipient in AD & find a DAG that recipient belongs to

• CAS server will attempt to route mail to a mailbox server in that DAG (preferably in the same site as the CAS server)

Routing Overview

DAG

Internet

Server

1 – Incoming mail on multi-role serverFrontend Transport receives

message on port 25... looks up where recipient’s mailbox exists and routes to a Transport service within the DAG for that mailbox

Transport receives message on port 2525… processes it and routes it to mailbox transport delivery on server where mailbox is active

Mailbox Transport Delivery receives the message on port 475… converts MIME to MAPI and delivers message to Store.

CAS 2013

Frontend Transport

MBX 2013

Store

Transport

Mailbox Transport

Scenario 1 – Protocol flow

Internet Frontend Transport

EHLO

250 OK

MAIL FROM

250 OK

RCPT TO

250 OK

DATA


Internet Frontend Transport Transport

EHLO

250 OK

MAIL FROM

250 OK

RCPT TO

250 OK

DATA (TLS Session)EHLO

XPROXYFROM

MAIL FROM

250 OK

RCPT TO

250 OK

DATA

250 OK

(EXCHANGEAUTH)250 OK

250 OK



EHLO

250 OK

MAIL FROM

250 OK

RCPT TO

250 OK


XPROXYFROM

MAIL FROM

250 OK

RCPT TO

250 OK

DATA

250 OK


250 OK

250 OKQUIT



EHLO

250 OK

MAIL FROM

250 OK

RCPT TO

250 OK


XPROXYFROM

MAIL FROM

250 OK

RCPT TO

250 OK

DATA

250 OK


250 OK

250 OKQUIT QUIT


TransportMailbox

Transport

(TLS Session)EHLO

MAIL FROM

250 OK

RCPT TO

250 OK

DATA

250 OKQUIT

XSESSIONSPARAMS


250 OK



EHLO

250 OK

MAIL FROM

250 OK

RCPT TO

250 OK


XPROXYFROM

MAIL FROM

250 OK

RCPT TO

250 OK

DATA

250 OK


250 OK

250 OKQUIT QUIT

MailboxTransport

(TLS Session)EHLO

MAIL FROM

250 OK

RCPT TO

250 OK

DATA

250 OKQUIT

XSESSIONSPARAMS


250 OK

Scenario 1 – Received headersReceived: from EXHV-1889.EXHV-5245dom.extest.microsoft.com (2001:4898:e8:3050:d9f3:8ace:7a2f:900b) by EXHV-1889.EXHV-5245dom.extest.microsoft.com (2001:4898:e8:3050:d9f3:8ace:7a2f:900b) with Microsoft SMTP Server (TLS) id 15.0.620.3 via Mailbox Transport; Sun, 27 Jan 2013 11:50:14 -0800Received: from EXHV-1889.EXHV-5245dom.extest.microsoft.com (2001:4898:e8:3050:d9f3:8ace:7a2f:900b) by EXHV-1889.EXHV-5245dom.extest.microsoft.com (2001:4898:e8:3050:d9f3:8ace:7a2f:900b) with Microsoft SMTP Server (TLS) id 15.0.620.3; Sun, 27 Jan 2013 11:50:13 -0800Received: from Internet (172.18.140.30) by EXHV-1889.EXHV-5245dom.extest.microsoft.com (10.176.198.88) with Microsoft SMTP Server (TLS) id 15.0.620.3 via Frontend Transport; Sun, 27 Jan 2013 11:50:10 -0800Subject: Incoming mail on all-in-one roleMessage-ID: <[email protected]>From: <[email protected]>

DAG

Internet

2 – Incoming mail to two recipients

CAS 2013

Frontend Transport

MBX 2013

Store

Transport

Mailbox Transport

Site

CAS 2013

Frontend Transport

MBX 2013

Store

Transport

Mailbox Transport

2 Recipients

Sit

e B

ou

nd

ary

Internet

DAG

3 – Originating mail to Internet

CAS 2013

Frontend Transport

MBX 2013

Store

Transport

Mailbox Transport

Site

CAS 2013

Frontend Transport

MBX 2013

Store

Transport

Mailbox Transport


EHLO

250 OK

MAIL FROM

250 OK

RCPT TO

250 OK

DATA

250 OK

(TLS Session)

QUITTransportMailbox Transport

(EXCHANGEAUTH)


250 OK

(TLS Session)

EHLO

250 OK

MAIL FROM250 OK

RCPT TO250 OK

DATA250 OK

QUITQUIT

XPROXYTO

MAIL FROM

250 OKRCPT TO

250 OKDATA

250 OK



250 OK

(TLS Session)

EHLO

250 OK

MAIL FROM250 OK

RCPT TO250 OK

DATA250 OK

QUITQUIT

XPROXYTO

MAIL FROM

250 OKRCPT TO

250 OKDATA

250 OK


Mailbox Transport

EHLO

250 OK

MAIL FROM

250 OK

RCPT TO

250 OK

DATA

250 OK

(TLS Session)

QUIT

(EXCHANGEAUTH)

Internet

DAG 2

CAS 2013

Frontend Transport

MBX 2013

Transport

Store

Mailbox Transport

DAG 1

4 – Originating mail to multiple recipients

CAS 2013

Frontend Transport

MBX 2013

Store

Transport

Mailbox Transport

Site

CAS 2013

Frontend Transport

MBX 2013

Store

Transport

Mailbox Transport

3 Recipients

Sit

e B

ou

nd

ary

Transport high availability

Shadow is done ONLY by the Transport service

Every message is redundantly persisted (shadowed) before its receipt is acknowledged to the sender

If shadow can’t be made, Transport service will reject sender with 450 4.5.1 response

Transport service will first attempt to shadow to an active server in another site (but in the same DAG); after which will try to shadow to any active server in DAG

Shadow server will periodically check with the primary server for a heartbeat; if no heartbeat for 3 hours, it will send message on behalf of primary

Duplicate delivery detection present in store; in case primary resends message

Shadow Messages

Transport service redundantly store all mail for a configured time span to protect against irrecoverable mailbox failures

Now has a “shadow” equivalent and is no longer a SPOF

Consolidates and improves E2010 Transport Dumpster functionalitySafety Net retains data for a set period of time, regardless of whether the message has been successfully replicated to all database copies or delivered to final destination

Processes replay requests by resubmitting messages from “primary” or “shadow” Safety Net for mailboxes fail overs or lag restores

To see various shadow & safety net values: get-transportconfig | fl *Shadow*,*safety* [ShadowHeartbeatFrequency; ShadowResubmitTimeSpan; SafetyNetHoldTime]

Safety net

DAG

Internet

All messages to Transport are shadowed

CAS 2013

Frontend Transport

MBX 2013

Store

Transport

Mailbox Transport

Site

CAS 2013

Frontend Transport

MBX 2013

Store

Transport

Mailbox Transport

S SSMTP

Sit

e B

ou

nd

ary



EHLO

250 OK

MAIL FROM

250 OK

RCPT TO

250 OK


XPROXYFROM

MAIL FROM

250 OK

RCPT TO

250 OK

DATA

250 OK


250 OK

250 OKQUIT QUIT

Scenario 1 – Protocol flow with shadow


EHLO

250 OK

MAIL FROM

250 OK

RCPT TO

250 OK


XPROXYFROM

MAIL FROM

250 OK

RCPT TO

250 OK

DATA


250 OK

Transport(MBX Svr1)



EHLO

250 OK

MAIL FROM

250 OK

RCPT TO

250 OK


XPROXYFROM

MAIL FROM

250 OK

RCPT TO

250 OK

DATA


250 OK

Transport(MBX Svr1)

Transport(MBX Svr2)

(TLS Session)

EHLO

MAIL FROM

250 OK

RCPT TO

250 OK

DATA

(EXCHANGEAUTH)

XSHADOWREQUEST

250 OK

QUIT



EHLO

250 OK

MAIL FROM

250 OK

RCPT TO

250 OK


XPROXYFROM

MAIL FROM

250 OK

RCPT TO

250 OK

DATA


250 OK

Transport(MBX Svr1)

Transport(MBX Svr2)

(TLS Session)

EHLO

MAIL FROM

250 OK

RCPT TO

250 OK

DATA

(EXCHANGEAUTH)

XSHADOWREQUEST

250 OK

QUIT250 OK250 OKQUIT QUIT

Shadow Message – SMTP ‘ping’

Transport(MBX Svr1)

Transport(MBX Svr2)

Shadow server will ‘ping’ the primary server every 2 min (default)

If primary server has delivered the message it will inform the shadow with a 250 OK + Message GUID

Shadow server will place message in shadow safety net

(TLS Session)

EHLO

(EXCHANGEAUTH)

XSHADOW

QUIT

XQDISCARD

250 OK (MSG ID)

250 OK (MSG ID)

250 OK

(TLS Session)

EHLO

(EXCHANGEAUTH)

XSHADOW

QUIT

XQDISCARD

250 OK (MSG ID)

250 OK

Message Tracking Log

Message Delivery

Message Submission

FrontEnd Transport

Transport Transport

MBX Transport

MBX01 MBX02 MBX03

CAS

2

SMTPRECEIVE

1

3

4

5

SMTPSEND

STOREDRIVERDELIVER

SMTPHARECEIVE

SMTPHADISCARD

SMTPHAREDIRECT

...

FrontEnd Transport

Transport Transport

MBX Transport

MBX01 MBX02 MBX03

CAS

4

5

3

2

1

SMTPHARECEIVE

SMTPHADISCARD

SMTPHAREDIRECT

STOREDRIVERRECEIVE

STOREDRIVERSUBMIT

SMTPRECEIVE

SMTPSEND ...

SMTP Client Submission

Client SubmissionUsed by customers that have SMTP clients such as Thunderbird, Outlook Express, etc.

Clients use SMTP for sending email; but POP/IMAP for retrieving mail from their mailbox

Emails sent via client submission do not get stored in ‘sent items’ folder of the mailbox

DAG2 DAG2 DAG1

CAS 2013Frontend Transport

M1 M2 M3 M4

DAG1

CAS 2013Frontend Transport

M5

Site 2

M6 M7 M8

mail.fabrikam.com

Client submission to single namespace

Site 1 Sit

e B

ou

nd

ary

Client Submission – Protocol flow

SMTP Mail Client

EHLO

250 OK

MAIL FROM

250 OKRCPT TO

250 OKDATA

AUTH

( TLS Session)

250 OK

( TLS Session)

XPROXY250 OK

MAIL FROM250 OK

RCPT TO250 OK

DATA250 OK250 OK

QUITQUIT

Frontend Transport

TransportMailbox Transport

In review: session objectives and takeawaysSession objective(s): Understand the different transport components in CAS and MBX rolesUnderstand key architectural improvements made in EX2013Understand key mail routing scenarios

All mail communication between servers is SMTPSubmission and delivery to a mailbox is always localMail is routed to the DAG where the recipient belongsImproved shadow redundancy & safety net protects messages during and after delivery

Questions?

Experts Unplugged: Architecture Transport & Hygiene [10:45am – 12pm Tuesday]

Experts Unplugged: Architecture Transport & Hygiene [8:30am – 09:45am Wednesday]

Unplugged Sessions

1. Go to the Pre-Release Programs Booth

2. Tell us about your Office 365 environment/or on premises plans

3. Get selected to be in a program

4. Try new features first and give us feedback!

Start now at:http://prereleaseprograms-public.sharepoint.com/

Pre-Release Programs TeamBe first in line!

© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. 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 provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Documents

Overview of Exchange 2013 Architecture Transport components shipping with Exchange 2013 Mail Routing Scenarios Transport High Availability SMTP Client