How do I create multiple HELO records on Exchange Server 2007

If each of these connectors sending mail for a different domain?  The way to differentiate between send connectors is to have separate address spaces, one can route mail for *.mydomain1.com and the other can route for *.mydomain2.com.  To do this, create two send-connectors and give each one a different address space.

Is it really as simple as that? I will go ahead and try that but Im sure that I have tried that one already, I thought that the address space in the send connector was what Domains the exchange box can send to? The default connector is * in address space which I thought meant that it can send to any Domain?

Hi Julian, I have just tried inputting a Domain in the address space and it doesnt allow the email out to my personal domain but when I put * in it does. Are you sure you have this right? Do I need to be restarting any services after putting in the address spaces?

If you are sending to domain @domain.com then you put the domain *.domain.com or (*domain.com) in the address space for the send connector. Note that the connector checks the domain you are sending TO, not where the mail is coming FROM.

You should restart the transport service.

So Im not sure why I am putting in the address spaces in the send connectors? I need to have seperate HELO FQDN's as if I send from Domain 2 then it is tagged with HELO of FQDN of Domain 1 which in time could mean that Domain 2 is blacklisted. I have scoured the internet in search of blogs etc that may help and have also looked on TECHNET but apart from creating scripts to change the SMTP header when an email is sent out from Domain 2 I havent found any usable answer.  

Your comment is interesting. Stepping back, could you explain why you want different HELO FQDNs? I'd like to understand the scenario better.

When you send an email it contains a HELO record in the header of the email which in turn contains the FQDN.  The problem is that some ISPs look at the header and if the sending Domain does not match the HELO FQDN then the email is bounced and in some cases can end up with the sending Domain being black listed.  This is why I need seperate FQDN HELO records for each Domain I am sending from.  Hopefully this explains further what the issue is?

Thank you, that clarifies what you're trying to do. Given that, my earlier comment is important to highlight: "Note that the connector checks the domain you are sending TO, not where the mail is coming FROM." Given that, if you put the address space *.mydomain1.com in the send connector the connector will only be used when you're sending TO mydomain.com, not FROM it. There's no way to configure the EHLO banner based on the domain the mail is coming from. That said, this isn't a problem if you since spam filters do not look at this. It's very common for a single mail server to send out mail from multiple domains, hosters such as Positini, Google, 1and1 etc.  do this all the time.

Here's a thread on this relating to reverse DNS, which is quite similar: https://www.experts-exchange.com/questions/23141108/Reverse-DNS-when-hosting-multiple-domains.html

In short, it's OK if the EHLO banner does not match the FROM domain.

"In short, it's OK if the EHLO banner does not match the FROM domain"

OK really?

I have seen many an ISP in the UK bounce messages based on the incorrect domain in the HELO/EHLO.  That said I agree that it is quite common to send out from differing domains from one server.  However given that ISPs certainly in the UK are starting to check the headers and doing a reverse lookup and also in some cases resulting in a domain being blacklisted then this is going to be quite a common request so I am looking for someone to answer it.  I cannot beleive that Microsoft have not thought of this and or that no one else has found a solution to this common problem that is going to become more of an issue in the future.

Note that you can make reverse DNS match up 100% of the time. You have one reverse DNS record that matches your outbound IP address and make sure the url listed in reverse DNS matches the EHLO url (even if the reverse DNS and EHLO urls don't match the FROM: domain for the email being relayed).

Hi Julian, I thank you for your advice but to be honest you havent told me anything that i didnt already know.  I am still awaiting an acceptable solution to be posted???

This question should be closed with no accepted solution rather than abandoned as I have not abandoned it I simply have not had an acceptable answer which is very dissapointing to say the least

Hi Demazter,

Not trying to be awkward here but have you read the original question?

My problem is that Domain 2 is sending emails out with Domain 1 as the HELO in the header and if an ISP carries out a reverse lookup it will fail on the sending Domain and the message will be bounced.

Yes I did read the question.

Hence my post!

You cannot add a second send connector, exchange will not allow you to determin the sending route based in the domain you are using to send.

The correct method is the one I posted above.

The rDNS is based in the A record used by MX so as long as it's setup as I have posted above it will match.

OK so what you are saying is that when the ISP carries out a reverse lookup on Domain 1 (as it will as this will be the domain in the HELO on the header) it will pass if I have an A record against domain 2?

This is not just about reverse lookup by the way, ISPs now check to see if the sending Domain matches the HELO record in the header of the email

Does that make sense now?

Will have a look at this later as I am in meeetings all afternoon

This question has been classified as abandoned and is being closed as part of the Cleanup Program. See my comment at the end of the question for more details.