Scribd
Upload
61 views7 pages

5 Message Flow and Queue

The document describes mail flow in an Exchange server organization. Mailboxes and mail transport are managed by mailbox servers running the Transport and Mailbox Transport services. For outgoing mail, messages are sent from user mailboxes to the Mailbox Transport Submission service and routed through the Transport service queues. For incoming mail, messages are received by the Front End Transport service and routed through the Transport service queues to the Mailbox Transport Delivery service and ultimately to user mailboxes. The Transport service performs categorization including recipient resolution, routing, and content conversion on messages in its queues.

Uploaded by

Gauri
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
61 views7 pages

5 Message Flow and Queue

The document describes mail flow in an Exchange server organization. Mailboxes and mail transport are managed by mailbox servers running the Transport and Mailbox Transport services. For outgoing mail, messages are sent from user mailboxes to the Mailbox Transport Submission service and routed through the Transport service queues. For incoming mail, messages are received by the Front End Transport service and routed through the Transport service queues to the Mailbox Transport Delivery service and ultimately to user mailboxes. The Transport service performs categorization including recipient resolution, routing, and content conversion on messages in its queues.

Uploaded by

Gauri
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

1.

We have mailboxes server HUB\CAS server and MTA of Cisco iron fort 160
and 170
2. We created send connector on our HUB\CAS server route mails through
smart host.
3. We have created receive connector receive mail these local IP
4. We have created A and MX recorders on our public DNS with our MAT host
name and route all mails by NAT.
My outgoing mails flow is
Outgoing message flow:-
1. When a user send message. It receive by mailbox server
2. Mailbox server notifies to HUB server by mail submission service that I have
a message.
3. HUB server pick that message from mailbox server (outbox) by store drivers
and put in submission queue
4. HUB server run categorization in submission queue and identifies
destination address.
i. Recipient resolution identifies the recipient location.
ii. Routing identifies a delivery path to the recipient. Based on the
routing path, a next hop destination is identified. The next hop
location could be one of the following:
1. If the recipient cannot be identified, the message is placed in the
Unreachable queue.
2. If the next hop is a Mailbox server located in the same Active
Directory site, the message is placed in the Mailbox Delivery
queue.
3. If the next hop is a Hub Transport or Edge Transport server in
the same Active Directory site, the message is placed in that
server's Submission queue.performs categorization, and
queues the message for further delivery.
If the next hop is a remote Active Directory site, remote SMTP domain
name, or smart host, the message is placed in the Remote Delivery queue
that corresponds to the destination.
5. After indentify destination address of message. It take following action:-
i. If destination address is local it contact to DC
ii. DC resolve destination address
iii. After that hub send mail to users mailbox database
iv. If destination is outside. It send message to MTA.
v. MTA send our public DNS over NAT IP
vi. Public DNS resolve destination address and send to destination
address
vii. If destination address is another site it contact to DC or catalog
server and send message to another site Hub server
Note: - HUB server before send to next hop. It check transport rule. If transport
agent enable
Incoming message flow:-
1. public DNS receive mails from outside domains and send our MTA over
NAT IP.
2. MTA send mail to HUB\CAS server .( its match up recipient domain to
accepted domain. If domain is match )
3. HUB server put mails in submission queue and run categorization
4. After contact DC.
5. DC resolve destination address
6. After that hub send mail to users mailbox database

Qus. What is queue?


Ans. Queue is temporary location where all message wait for enter to next stage in
the transport line.
1. Mailbox submission queue:- in this queue all submit by HUB server run
categorization for determine destination address
2. Mailbox delivery queue:- this queue stores message that will be delivered to
mailboxes on mailbox server
Note :- Mailbox submission queue do not on ET server .
3. Remote delivery queue:- this queue store all message that send to remote
domain also ad site or another HUB server
4. Passion queue:- there specific message hat exchange server considers to
harmful to exchange system.
5. Unreachable queue :- this queue captain those message could not deliver to
their destination address.
Message Queue Facts

1. In the Exchange Management Shell, use the Suspend-Queue and Resume-


Queue cmdlets.
2. In the Exchange Management Shell, use the Retry-Queue cmdlet. You can also
use the Retry-queue cmdlet with the Resubmit parameter to return messages to the
Submission queue. You can do this for messages with the following status:
3. In the Exchange Management Shell, use the Suspend-Message or Resume-
Message cmdlets
4. In the Exchange Management Shell, use the Remove-Message cmdlet. The
-WithNDR
$true option sends the NDR, and the -WithNDR $false option does not send
the NDR
5. In the Exchange Management Shell, use the Export-Message cmdlet
6. Use Get-Message to view the details of one or more messages in a queue on
a Hub Transport server or an Edge Transport server.
7. Use Get-Queue to view the configuration of a queue on a Hub Transport
server or an Edge Transport server

Q. What is transport pipe line in exchange server?

Ans. it is a collection of services, connections, components and queues that work together to route
messages.
Mail flow of exchange server 2013

Exchange server 2013 use flowing services for route email:-

1. Front End Transport service


2. Transport service
i. Mailbox Transport Delivery
ii. Mailbox Transport Submission

Front End Transport service:-

1. Which runs on all Client Access servers, acts as a stateless proxy for all inbound and outbound
external SMTP traffic.
2. This service does not inspect message content but it can perform basic e-mail filtering based on
connections, domains, senders and recipients.
3. It only communicates with the Transport service on a Mailbox server and does not queue any
messages locally.

Transport service:-

1. It runs on all Mailbox servers and is almost identical to the Hub Transport server role in previous
versions of Exchange. It handles all SMTP mail flow for the organization, performs message
categorization and content inspection.
2. Unlike previous versions of Exchange, the Transport service never communicates directly with a
mailbox database, which is now handled by the Mailbox Transport service.
3. The Transport service routes messages between the Mailbox Transport service and the Front
End Transport service.

Mailbox Transport service: - it run on all Mailbox servers and is made of two separate services:

1. Mailbox Transport Delivery service: -it receives SMTP messages from the Transport service and
connects to the mailbox database using an Exchange Remote Procedure Call [RPC] to deliver the
message.
2. Mailbox Transport Submission service: -it connects to the mailbox database using RPC to
retrieve messages and submits them to Transport service. The Mailbox Transport service also
does not queue any messages locally.

SMTP Receive: When e-mails are received by the Transport service, content inspection is performed,
transport rules are applied and anti-spam/anti-malware inspection is performed (if enabled). If the e-
mail is not rejected after passing through SMTP Receive, it is put in the Submission queue;

Submission is the process of putting e-mails into the actual Submission queue and can happen in three
different ways:

1. Through an SMTP Receive connector;


2. Through the Pickup and Replay directories which now reside on Mailbox servers;
3. Through an agent.

SMTP Send: depending on the location of the message recipient, the message is routed to:

1. Mailbox Transport service on the same Mailbox server;


2. Mailbox Transport service on a different Mailbox server that is part of the same DAG;
3. Transport service on a Mailbox server in a different DAG, AD site, or AD forest; or
4. Front End Transport service on a Client Access server for delivery to the Internet.

Massages are entering in exchange organization by four ways:-

1. Through a Receive connector;


2. Through the Pickup and Replay directories;
3. Through the Mailbox Transport service
4. Through agent submission.
5.
Categorizer performs below three step in Submission queue:-
1. Recipient Resolution: this process resolves e-mail address and determine recipient mailbox that
internal or external.
2. Routing Resolution: after recipient resolved. Message is routed to next hop. Next hop could be
……
3. Content Conversion: it a is the process of correctly formatting a message for each recipient like
HTML, rich text format or plain text. Transforming e-mail messages from one format to another
format such as MAPI to MIME, UUENCODE to base64 encoded.
Outgoing:

Mailbox outboxStore Driver Submit Mailbox Transport Submission Servicereceive connector 


Submission Queue Categorization (Name Resolution  routing  content conversion)  deliver
Queue (Remote queue, Mailbox Queue)  Front end transport service

Incoming:

Front end transport service  receive connector  Submission Queue Categorization (Name
Resolution  routing  content conversion)  deliver Queue ( Mailbox Queue)  Mailbox Transport
Delivery Service  Store Driver Deliver  RPC  Mailbox Database
Figure 1.2

You might also like