SMTP Protocol vs. SMTP Connector

SMTP Protocol vs. SMTP Connector

Post by Sm9ybWEgSy » Wed, 04 Apr 2007 05:24:03


We recently upgrade to Exchange Server 2003. The consultant configured SMTP
using SMTP Protocol. Our old Exchange 5.5 server used a connector instead,
the Internet Exchange service if I recall correctly. Is there a preference
for using either the protocol or the connector? Also, should only one method
be used as opposed to both at the same time?

The reason I'm interested in the connector is that it permits delivery
restrictions.
 
 
 

SMTP Protocol vs. SMTP Connector

Post by Bharat Sun » Wed, 04 Apr 2007 08:22:22

SMTP Virtual Servers are protocol listeners that are bound to particular IP
address and port. As such, they listen to inbound SMTP traffic. Out of the
box, SMTP Virtual Servers can be used to route outbound internet traffic if
the server can resolve internet domains and has outbound SMTP connectivity
(port 25).

SMTP Connectors are a group of settings that dictate how outbound mail is
set to particular domains e.g. microsoft.com, or *to all domains that are
not local and for which there are no specific Connectors* - this is done by
using/creating a SMTP Connector for the address space *. SMTP Connectors use
SMTP Virtual Servers as "bridgeheads" to route outbound mail. You can have
more than one bridgeheads on a SMTP Connector, and you can have multiple
Connectors for the same address space but with same or different costs
(load-balance or fail-over).

As such, it's a best practice to create Connectors for routing outbound
mail, particularly when routing mail through non-Exchange SMTP hosts (aka
"smarthosts"). Some settings are common between the two - in case these
conflict, for outbound mail the Connector's settings will override the
Virtual Server's.

--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
exchangepedia.com/blog
------------------------------