TABLE OF CONTENTS The Exchange 2007 Hub Transport server role should be installed on a domain-member server, and should always be deployed on your internal network, not in the perimeter network as some might. The Hub Transport server replaces the bridgehead server we know from Exchange 2000 and 2003, and therefore takes care of all the internal mail flow in the organization. All internal messages will pass through the Hub Transport server, even if the sender and recipient mailbox are located in the same AD site heck, even if they ve on the same Mailbox server!
In addition to being responsible for all mail flow inside the organization, the Hub Transport server has a set of transport agents that lets us configure rules and settings that can then be applied as messages pass through the server. The Hub Transport server also allows us to create messaging policies and rule settings that match the specific regulations and compliance requirements in the organization.
Since the Hub Transport server typically sends and receives Internet messages through an Edge Transport server in the perimeter network, it doesn t have any anti-spam agents installed, and doesn t allow inbound messages from unauthenticated (untrusted) e-mail servers on the Internet at least not in its default state. Since not all organizations can, nor will, deploy an Edge Transport server in their perimeter network, I ll show you how you can configure the Hub Transport server to be the Internet-facing transport server in your organization.
A lot has...
