??‘ Through placement of messages in the Submission queue by the store driver.
??‘ Through message submission via an agent.
In a nutshell, when a message is received by transport either through SMTP communication with
another mail host or dropped into the Pickup or Replay directories, it is placed in the Submission queue
to be picked up and processed by the Categorizer. The message recipients are resolved by the
Categorizer, the message is bifurcated, and it goes through content conversion, after which its route is
determined. If the message is bound for a mailbox on a Mailbox server in the local Active Directory site,
it is routed via the MAPI Delivery and placed in the user ??™ s inbox by the store driver component. If the
message is to be routed to a user outside the local Active Directory site or organization, message delivery
is SMTP - based and would be routed via the Remote Delivery queue to a Hub Transport server in
Chapter 7: Confi guring the Hub Transport Role
197
another Active Directory site, or to an Edge Transport server for Internet delivery. The message can also
be routed directly from the Hub Transport server if no Edge Transport server is configured.
Configuring the Hub Transport Server
The Hub Transport server implements the core transport functionality and is responsible for all message
flow within an Exchange organization.
Pages:
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299