#Mailplane schedule functionality how to

The only communication that always occurs on the local Exchange server is between the Mailbox Transport service and the local mailbox database.

The following diagram shows the relationships among the components in the Exchange transport pipeline.Īlthough the diagrams in this topic show the components on a single Exchange server, communication also occurs between those components on different Exchange servers. This service is described in more detail later in this topic. If you have an Edge Transport server installed in the perimeter network, all mail coming from the Internet or going to the Internet flows through the Transport service Edge Transport server. Transport service on Edge Transport servers: This service is very similar to the Transport service on Mailbox servers. It also doesn't queue any messages locally. The Mailbox Transport service doesn't communicate with the Front End Transport service, the Mailbox Transport service, or mailbox databases on other Mailbox servers. Mailbox Transport Delivery service: This service receives SMTP messages from the Transport service on the local Mailbox server or on other Mailbox servers and connects to the local mailbox database using RPC to deliver the messages. The Mailbox Transport Submission service has access to the same routing topology information as the Transport service. The service submits the messages over SMTP to the Transport service on the local Mailbox server or on other Mailbox servers.

Mailbox Transport Submission service: This service connects to the local mailbox database using an Exchange remote procedure call (RPC) to retrieve messages. Mailbox Transport service on Mailbox servers: This service consists of two separate services: The Transport service on Mailbox servers is described in more detail later in this topic. The Transport service routes messages among the Mailbox Transport service, the Transport service, the Front End Transport service, and (depending on your configuration) the Transport service on Edge Transport servers. That task is now handled by the Mailbox Transport service. Unlike Exchange 2010, the Transport service never communicates directly with mailbox databases. The Transport service handles all SMTP mail flow for the organization, performs message categorization, and performs message content inspection. Transport service on Mailbox servers: This service is virtually identical to the Hub Transport server role in Exchange Server 2010. The Front End Transport service doesn't inspect message content, doesn't communicate with the Mailbox Transport service, and doesn't queue any messages locally. The transport pipeline consists of the following services:įront End Transport service on Mailbox servers: This service acts as a stateless proxy for all inbound and (optionally) outbound external SMTP traffic for the Exchange Server organization.

#Mailplane schedule functionality how to

The transport pipeline is a collection of services, connections, components, and queues that work together to route all messages to the categorizer in the Transport service on an Exchange Mailbox server inside the organization.įor information about how to configure mail flow in a new Exchange 2016 or Exchange 2019 organization, see Configure mail flow and client access. In Exchange Server, mail flow occurs through the transport pipeline.