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

Send Connectors for Multiple Domains

I have Exchange Server 2007 setup to receive emails for 2 domains.  When email goes out for one of those 2 domains I need it to go out on its own send connector.  The reason - so I can set the HELO or EHLO response to the appropriate domain name.
Is this possible?
0
tfountain
Asked:
tfountain
  • 2
  • 2
1 Solution
 
SembeeCommented:
Exchange doesn't route email based on the sender. It only routes email based on the recipient. What you want to do is not going to be possible.

What I do (which is the same that I did on Exchange 2003) is use the same DNS information for all domains. SO the MX records etc are using the same hosts. This allows the use of one reverse DNS, one IP address etc for as many domains as I like.

Simon.
0
 
tfountainAuthor Commented:
I understand how you have set that up but how do you address HELO and EHLO along with Sender ID's?

i.e Say that I have 2 domains that I receive and send mail from: mail.mydomainA.com and mail.mydomainB.com.  I use the same IP and setup a rev DNS for them.  Then I route them both out through mail.mydomainA.com.  If I send a message from mail.mydomainB.com  and an ISP does a sender ID lookup and or HELO or EHLO, they will get mail.mydomainA.com and reject it. (ISP's that are starting to use this form of spam protection: Hotmail, AOL, MSN, Google...)

This has been an thorn in my side for several of my customers who have Exchange Servers with multiple domain names.

Is my line of reasoning correct or am I missing something?
0
 
SembeeCommented:
The ISP or whoever is receiving the email doesn't care who the email has come from.
As long as the sending server is setup correctly with matching DNS, forward DNS and ehlo. SenderID is one of those nice to have, but does not stop your email from flowing. It is like SPF, another nice idea but isn't used enough. None of the major email providers will block legitimate email, their customers will leave in their droves.
I don't deploy Sender ID or SPF on any Exchange deployment I do, and have no problems getting email delivered to aol.com - which is the most difficult one to get delivered to.

So in your scenario - mail.domainb.com wouldn't exist. The MX records for domainb.com would be mail.domainb.com. I have six domains on my home Exchange server, all of which have identical MX records. Most hosting companies will have all of their domains going to the same server.

Simon.
0
 
tfountainAuthor Commented:
Thank you.
0

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

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