Routing Groups + Default SMTP Virtual Server in Exchange 2003
Posted on 2005-04-28
I would like to know why is it best practice to create a Routing Group Connector to deliver External Mail rather than configuring the Default SMTP Virtual Server under protocols of Exchnage Server Name, under Protocols then SMTP?
The resaon I ask this question is that I need to deploy a SMTP Gateway called Policy Patrol Enterprise in our mail infrastructure. However for the SMTP Gateway to function, you need to to to allow incoming mail to be routed to the Exchange Server and outgoing mail to the appropraite ISP using the SMTP Virtual Server using IIS on the SMTP Gateway.
I have managed to configure the SMTP Server (Policy Patrol) to receive incoming mail and deliver it to the Exchange Server, however as the Exchange Server was not built by myself, so therefore I am having trouble understanding why there is an Routing Group Connector made for External Mail Delivery?
I know you can configure External mail delivery using a Routing Group Connector or simply configure the Default SMTP Virtual Server, under (Expand the Servers node. Double-click on <Exchange Server name> > Protocols > SMTP. Right-click Default SMTP virtual server and select Properties, select Delivery Tab, then Advanced and then specify server name in the Smart Host).
The routing group connector is working currenlty for us, however I am trying to undertand why is the Default virtual Server, under Server Name was not configured?
Is there a reason why external mail delivery is always best to be setup using a Routing Group Connector?
Any help to understand this difficulty would be much appreciated.