Figure 7 - 3
shows two Remote Delivery queues, one with a deliverytype of SmtpRelayToRemoteAdSite to
a Hub server in a different Active Directory site and another with Deliverytype called
SmtpRelayToTiRg with the next hop being an Exchange 2003 server in the ???First Routing??? group.
The MapiDelivery queue shown is discussed shortly.
Chapter 7: Confi guring the Hub Transport Role
195
Figure 7-2
Figure 7-3
Part II: Working with Server Roles
196
Figure 7-4
Finally, after successful delivery, the message is removed from the transport pipeline.
Please note that there are some Unified Messaging and Client Access instances that do not interact
directly with the transport pipeline. When a sent message is finally put in the outbox on behalf of the
sender, processing occurs by the same process as the submission process described previously.
To view the Hub Transport pipeline, use the Get-TransportPipeline cmdlet as shown in
Figure 7 - 4 . The TransportPipeline cmdlet also exposes two transport agents installed by default on
the Hub Trans port server: the Journaling Agent and the Transport Rule Agent. Agents are reviewed
in Chapter 9 .
Messages can enter the transport pipeline through any of four methods:
??‘ Through an SMTP Receive Connector communicating on port 25.
??‘ Through message files dropped into the Pickup or Replay directories.
Pages:
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298