Solved

Send Connectors for Multiple Domains

Posted on 2007-11-27
4
1,441 Views
Last Modified: 2010-04-21
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
Comment
Question by:tfountain
  • 2
  • 2
4 Comments
 
LVL 104

Accepted Solution

by:
Sembee earned 300 total points
Comment Utility
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
 

Author Comment

by:tfountain
Comment Utility
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
 
LVL 104

Expert Comment

by:Sembee
Comment Utility
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
 

Author Closing Comment

by:tfountain
Comment Utility
Thank you.
0

Featured Post

Integrate social media with email signatures

Is your company active on social media? Do you also use email signatures? Including social media icons in your email signature is a great way to get fans for free. Let all your email users know you’re on social media quickly and easily, in a single click.

Join & Write a Comment

Easy CSR creation in Exchange 2007,2010 and 2013
Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
This video discusses moving either the default database or any database to a new volume.

771 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

8 Experts available now in Live!

Get 1:1 Help Now