Solved

Exchange 2003 - Multiple SMTP Connectors

Posted on 2009-05-20
1
417 Views
Last Modified: 2012-08-14
Hello! We currently have one SMTP Connector (this is Exchange 2003 Enterprise, SP2) that forwards everything (*) to an external SmartHost, Cost 1. The SmartHost is an external mail filtering company. This works fine now...internal email stays internal, and all outbound goes to the filtering service.

I am adding a second SMTP Connector as we have one customer that requires TLS encrypted emails.I know I have to create a second SMTP Connector, add the customer domain to it (i.e., companydomain.com), check the TLS box, and also forward it off the same email filtering company.

My question is around the cost...do I need to change the default cost of 1 on either connector? I read somewhere you should, but I read other articles that say Exchange automatically looks for the Connector that best suits and just uses that (so keep them both at 1).

So this is how it will look:
Connector 1: Forwards outbound to filtering company, *, Cost 1
Connector 2: Forwards outbound to filtering company, comanydomain.com, Cost 1

Any ideas are appreciated. Thanks!
0
Comment
Question by:exadmin2006
1 Comment
 
LVL 18

Accepted Solution

by:
flyingsky earned 250 total points
ID: 24434923
you can leave both at 1, this is what MS said
"The address space defines the mail addresses or domains for the e-mail messages that you want to route through a connector. For example, an address space of * (asterisk) encompasses all external domainsthis connector is used to route all external e-mail. If you created a second connector with an address space of *.net, Exchange would route all mail sent to a domain with a .net extension through the second connector. This action occurs because Exchange selects the connector that has the most similar address space. This setting is configured on the Address tab of the SMTP connector's properties. "
http://technet.microsoft.com/en-us/library/aa997032(EXCHG.65).aspx
0

Featured Post

Too many email signature changes to deal with?

Are you constantly being asked to update your organization's email signatures? Do they take up too much of your time? Wouldn't you love to be able to manage all signatures from one central location, easily design them and deploy them quickly to users. Well, you can!

Join & Write a Comment

Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
To show how to create a transport rule 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 >> Rules tab.:  To cr…
This video discusses moving either the default database or any database to a new volume.

758 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

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now