"In-depth Exchange 2013"11 Transport Architecture Part1

The person who has read the TechNet document must be familiar with the following diagram, which is a complete interpretation of the message transfer architecture for the entire Exchange 2013, with several components already briefly discussed in the previous chapter, but there are other components that deserve further discussion. First, let's talk about the important words that appear in the picture.

650) this.width=650; "Width=" 561 "height=" 475 "title=" image "style=" BORDER:0PX;WIDTH:642PX;HEIGHT:549PX; "alt=" image "Src=" http://s3.51cto.com/wyfs02/M02/6F/6A/wKioL1WbvCGhDg7VAAF6iPHdRgY884.jpg "border=" 0 "/>

1, "Agent" here refers to agents, not a proxy, that is, processing or transmitting a message of a piece of program code. The agents in the figure directly reflects exchange's business logic, such as Exchange's anti-spam and malware filtering components belonging to the Protocol agent, the routing agent, the messaging agent, and the message submission agent as part of the message transport lifecycle. Basically, in addition to anti-spam and malware filtering related agents, you cannot directly add, remove, or configure these proxies. Of course, Microsoft has provided a range of APIs for developers to develop specific-purpose transport agents.

2, for Exchange Administrators, "queue (Queues)" is a very familiar noun. As the name implies, the queue implements such an orderly and predictable message-delivery arrangement logical schema through first-out (FIFO) principles. For each destination, 20 messages can be accommodated in each connection queue. For example, if you now have 80 messages to go to the contoso.com domain, Exchange will open 4 connections and attempt to post 1th, 21st, 41st, and 61st emails. Then, depending on the size of the message, 21-40 of the message may arrive at the destination before the 1th message. There are many different message queues in Exchange 2013 than in previous versions, which are described in detail below

3. Events, the event, triggers the event to drive agents and services to work. For example, in a message is queued up to send, in fact, this process is generally the case, a message click Send, was hit onmessagesend mark, Onmessagesend Mark was cleared, into the queue, ready to send.

OK, perhaps the above concept is still somewhat complex, we see, inside using the Get-transportpipeline command to obtain the current full role Exchange2013 server in the transport pipeline in the transport agent. When an event on the left side occurs, one of the transport agents on the right starts to process the message on that tag.

650) this.width=650; "height=" 294 "title=" clip_image004 "style=" border:0px; "alt=" clip_image004 "src=" http:/ S3.51cto.com/wyfs02/m02/6f/6d/wkiom1wbulprz1cgaaeafuwafiu219.jpg "border=" 0 "/>

Microsoft has defined four main tasks for the transport service in Ex2013 MBX, one or more components for each task, and I am here to post the original TechNet text, which has been written very clearly:

1. SMTP receive When a message is received by the transport service, a message content check is performed, the transport rule is applied, and anti-spam and anti-malware checks are performed (if enabled). an SMTP session contains a series of events that work together in a specific order to validate the contents of a message before it is accepted. after the message is fully delivered through the SMTP receive feature, the message is placed in the submission queue if the receiving event or the anti-spam and antimalware agents do not reject the message.

2. submitting A submission is the process of putting the message into the submission queue. The categorizer picks up one message at a time to categorize it. Submissions are done in the following three ways:

a) for SMTP reception via the Receive connector .

b) through the pickup directory or replay directory. These directories exist on mailbox servers and Edge Transport servers. A properly formatted message file that has been copied to the pickup directory or the replay directory is placed directly in the submission queue.

c) through the transport agent.

3. the categorizer sorting program picks up one message at a time from the submission queue. The categorizer completes the following steps:

a) recipient resolution, which includes top-level addressing, expansion, and recipient splitting.

b) Route resolution.

c) content conversion.

d) In addition, mail flow rules defined by the organization are applied. When a message is categorized, it is placed in a delivery queue that is based on the message destination. Messages by Destination mailbox database,DAG,Active Directory site,Active Directory queue to a forest or external domain.

4. how SMTP sends messages from the transport service depends on the location of the mail recipient relative to the mailbox server where the classification resides. Messages can be routed to the following location:

a) the Mailbox transport service on the same mailbox server.

b) The Mailbox transport service on different mailbox servers that belong to the same DAG.

c) different dags,active Directory sites, or active the Transport service on a mailbox server in the Directory forest.

d) delivery to the Internet through a Send connector on the same mailbox server, a transport service on a different mailbox server, a front end transport service on a client Access server, or a transport service on an Edge Transport server in a perimeter network .

After reading the contents of the four tasks, and then go back to look at the picture, is not immediately clear a lot?

Let's talk a little bit more about the interesting details of this picture:

1. If there are multiple MBX servers in the target delivery Group, the mailbox Transport submission service will select one of them on the basis of load balancing.

2. Earlier versions of Exchange support interactive services with third-party mail applications, but in Exchange2013 if you want to continue to use these mail app services, it's a good idea to adjust them to use SMTP. (e.g. fax, Lotus Notes)

3. When the sorter-Categorizer expands the list of recipients in the message, the transport service begins to apply the mail rules and archive rules.

4. All mailbox servers share some common transport configuration, such as the message size for Exchange Maximum transmission, the maximum number of recipients for inbound messages, which connectors are available (including connectors on the edge of Ex2010 and Ex2013), and so on. These configurations are present in AD, and the transport and archive rules are stored in the ad, and these settings can be configured using the Set-transportconfig command.

5, then the previous transport rule is stored in the ad, if the enterprise Exchange in a coexistence environment, then the transport rules will be stored in the ad in the version-named container; and then when you install Exchange2013, Will copy the existing earlier version of the Transport and archive rules from the previous version of the container to the new version of the container, so that Exchange 2013 can also implement the previous Exchange version of the transport rules, does not mean that the previous version and Exchange2013 transport rules are so synchronized. After a transport rule is created in Ex2013, these new rules will be hit with the version number of Exchange stamp,exchange2010 will ignore these new versions of the rules, so there is no rule violation. This mechanism is necessary because Ex2013 adds many new elements and actions to the transport rules. Therefore, in a hybrid environment, it is best to move the transfer process from the earlier Exchange version to the new Exchange server as much as possible.

Part1 first here, Part2, let's talk about the four components in Exchange 2013:

Front end transport front end Transport, transport service Transport, Mail transfer submission mail Transport submission, and mail transfer delivery mail Transport Delivery. The light reading is very clumsy ...

Extended read:

1. Transport Agent: https://technet.microsoft.com/zh-cn/library/bb125012 (v=exchg.150). aspx

2, mail flow: https://technet.microsoft.com/zh-cn/library/aa99634 (v=exchg.150). Aspx#transportpipeline

This article is from the "Castamere Rainy season" blog, be sure to keep this source http://sodaxu.blog.51cto.com/8850288/1671795

"In-depth Exchange 2013"11 Transport Architecture Part1