MSExchange SMTP Receive Connectors

Posted on 2009-07-02
Last Modified: 2012-05-07
We are running SBS 2008 (Exchange 2007) we have 2 SMTP Receive connectors one hosting our mail eg (not our real domain name) and a second receive connector which is a relay connection eg  When we restart our server for whatever reason, we intermittently have the second relay connection start as our primary smtp receive connector.  In order to get things working as expected we restart all exchange services and the correct one starts as the primary connector.  

While this is very intermittant - probably because it is a 50/50 chance of the wrong connector starting first - we previously had 2 other connectors - the Windows SBS Fax Sharepoint Receive and the Windows SBS Internet Receive and we are looking at re-instating at least 1 of these two which would increase the chance of the incorrect connector starting up.  

Question by:trimblenet
  • 3
  • 2
LVL 37

Expert Comment

by:Jamie McKillop
ID: 24787911

I'm not sure you have your receive connectors configured. There is no such thing as a "primary connector". Each connector needs to be running on a different port or IP. You can't have two connectors listening on the same port on the same IP. Are you using multiple IPs? If so, you probably have both connectors set to use "All available IP addresses". Change this so that the IP associated with the connector is specified.


Author Comment

ID: 24790599
we are using the same ip for our external connectors - one connector is using port 3325 the other port 25, the other connector is the internal connector servername.domainname.local

so we have port 25 port 3325
server.domain.local port 25 (i believe)

last night for example after we rebooted the server when telnetting to on port 25 we would always be welcomed with the header server.domain.local and emails would bounce back with a relay denied message as the mail was expecting to reach and was receiving a response from server.domain.local

hope this helps
LVL 37

Accepted Solution

Jamie McKillop earned 500 total points
ID: 24790649
That's your problem. You have two connectors on the same port and same IP. You either need another IP or you need to change the port used by server.domain.local. Since this is SBS, I assume it is your only Exchange server, so changing the port won't create any problems.


Author Comment

ID: 24791762
Hi JJ, Thanks for the response.  I have never seen this issue on othersites.  So your suggesting we shouldn't have any problems by changing the port for the internal connector to say 4425?

LVL 37

Expert Comment

by:Jamie McKillop
ID: 24793351
You can change the port to any port than isn't currently used by the server.


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!

Question has a verified solution.

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

Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
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…
This video discusses moving either the default database or any database to a new volume.

910 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

24 Experts available now in Live!

Get 1:1 Help Now