The Experts below are selected from a list of 6 Experts worldwide ranked by ideXlab platform
Tony Redmond - One of the best experts on this subject based on the ideXlab platform.
-
Getting the Mail through—Routing and Message Delivery
Tony Redmond's Microsoft Exchange Server 2003 with SP1, 2020Co-Authors: Tony RedmondAbstract:The Exchange is used to deliver a message in a reliable and robust manner through routing and transport engine. Message routing encompasses three major tasks: server to server message delivery, routing between different groups of servers, and external and local message delivery. Exchange maintains destination queues for messages sent to domains such as hp.com, as well as link queues for messages waiting to travel on the next link to their final destination. The queuing engine is supported by the QueueAdmin API that is used by the Exchange System Manager snap-in to view queue status. To categorized and route the message, a number of operation is performed. The Routing Engine writes information about categorization processing into the XEXCHS0 properties of messages, so that subsequent Exchange servers along the path do not repeat work. Servers in a routing group typically communicate through high-speed connections, so the definition of a routing group is very similar to that of an Exchange 5.5 site. IMF on the SMTP virtual servers handles message traffic.
-
Exchange and the Active Directory
Tony Redmond's Microsoft Exchange Server 2003 with SP1, 2005Co-Authors: Tony RedmondAbstract:This chapter discusses the Exchange and the active directory. Messaging Systems depend on directories for a variety of needs. Fetching email addresses for users and knowing what server their mailboxes are located on is perhaps the most obvious, but directories also hold large amounts of configuration data, such as how servers connect together and permissions. In the first generation of Exchange, the Directory Store (DS) held all of this data. The link between the DS and the other Exchange components, such as the Store and the MTA, that need to access directory data is simple, because all of the components reside on the same physical server. Exchange accesses DCs and GCs for different purposes. DCs provide essential System configuration data such as details of the servers and connectors installed within an organization. GCs provide information about user mailboxes and email addresses. The Routing Engine uses data taken from the GCs to route email, and MAPI clients, such as Outlook, use the same data as the Global Address List (GAL). Other clients use LDAP requests to search and retrieve information about recipients from the AD. Other examples of AD consumers include the Active Directory Connector, Recipient Update Service, and the Exchange System Manager (ESM) console.
