• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 475
  • Last Modified:

Exchange 2003 - Multiple SMTP Connectors

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
exadmin2006
Asked:
exadmin2006
1 Solution
 
flyingskyCommented:
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
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now