This implementation of the Edge Transport server new to the
Exchange line of messaging products arose as a result of increasing Unsolicited Commercial E -mail
(UCE) volume and the risk of denial of service attacks perpetrated via email. It reduces the attack
surface of such threats by providing a means for organizations to segment such email traffic even
before it enters the Exchange organization, while preventing access to internal resources. Some of
the features of the Edge Transport server have been implemented in earlier versions of Exchange,
however this role segmentation was never possible in any other version of Exchange. Message
filtering functionality such as sender, Recipient, connection filtering, and so forth, which existed in
Exchange Server 2003, have been improved and implemented on the Edge Transport server role.
By the end of this chapter, you ??™ ll have an overview of the components of the Edge Transport server
and be able to configure the Edge Transport server for email message flow into and out of an
Exchange organization, using the Exchange Management Shell. You will also gain an idea of how
agents work in message hygiene.
This chapter covers the following:
??‘ A brief overview of the Edge Transport server role and its architecture
??‘ The Active Directory Application Mode (ADAM) service requirement for the Edge
Transport server role
??‘ Configuration of the Edge Transport server
??‘ Message hygiene and transport agents
Part II: Working with Server Roles
236
The following is a list of Edge - related cmdlets that could be used to view and configure the Edge
Transport server role in Exchange Server 2007.
Pages:
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340