Routing Groups + Default SMTP Virtual Server in Exchange 2003

Posted on 2005-04-28
Medium Priority
Last Modified: 2008-02-01

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.

Thank you

Question by:AJAY_MASSON
1 Comment
LVL 21

Accepted Solution

marc_nivens earned 2000 total points
ID: 13885758
First, it is not best practice to use a routing group connector for internet mail.  This connector is for connecting 2 Exchange 2000+ routing groups.  An SMTP connector is better suited for internet mail.  As far as why a connector is better than configuring the Default SMTP virtual server, the answer is twofold.  

1)  You have multiple servers and want to control which one sends internet mail (called a bridgehead).  Without a connector each server tries to send the message out itself.
2)  Some of the options on the SMTP VS just don't work as well as when a connector is used (like alternate DNS servers and forward unresolved recipients)

However, if you only have 1 server and the only option you're changing on the SMTP VS is the smarthost it should work fine.  An SMTP connector just gives you more options like the ability to use HELO instead of EHLO for compliance with older systems.

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Eseutil Hard Recovery is part of exchange tool and ensures Exchange mailbox data recovery when mailbox gets corrupt due to some problem on Exchange server.
There can be many situations demanding the conversion of Outlook OST files to PST format and as such, there is no shortage of automated tools to perform this conversion. However, what makes Stellar OST to PST converter stand above the rest? Let us e…
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
Suggested Courses

864 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question