Exchange 2010 Send Connector with narrow address space not being used

On the Network tab of the new send connector where are you telling it to route mail to?

Should have added the following:
Your addfress space is *.domain1.com ... and have you set any authentication i.e. none
And an obvious one, you've enabled the connector? Sorry if these are obvious questions we route specific domains from 2010 to sendmail boxes and I'm just running through what I would check

PYThePorkpie

Many thanks for your reply.
To answer your questions.
Yes, authentication is set to None. On the Network tab, I am using "Route mail through the following smart hosts" where the IP address of my IronPort (e-mail gateway) is listed in square brackets. No other settings configured on this tab. And yes, the connector is enabled.

ExchangePandit

Thank you for your question. I believe I might have misread/misunderstood the purpose of the address space configuration of a Send Connector. Reading it again, it clearly states "The address space for a Send connector specifies the recipient domains to which the Send connector will route e-mail". That is not what I initially thought.

You are correct, domain1.com is one of my own domains which I send & receive e-mails using my Exchange infrastructure.

As I am introducing a new e-mail gateway (new IronPort), I was planning on performing some extensive testing on this device by routing e-mails for domain1.com through this gateway; both external incoming e-mails as well as internal e-mails going out of the organisation. External incoming e-mail is fixed as my MX record is updated. I am just trying to figure out how I can also route external e-mails from this domain through this new e-mail gateway.

Is this possible at all?

Thanks again ExchangePandit for pointing this out.

Here is answer on internal emails:

http://technet.microsoft.com/en-us/library/aa996349.aspx (read the first paragraph please)

I hope I have answered your question here with the above link.

Also see different types of connectors and when they will be used:

Custom: Custom options are used when you wanted to send mail to a specific domain which is not an Exchange Server. Custom connectors are used for forwarding messages to a smart host, which are configured to use DNS MX records to deliver the email to their destination.

- Internal: Internal connector is used when you want your Exchange Server to communicate with other Exchange severs in different forests. Eg. If there are multiple Exchange forests in your organization and you want communication between the multiple forests to follow a specific path then an Internal connector is the way to define that path.


- Internet: An Internet connector is used to send email directly to the Internet, and is configured to use DNS MX records to route email to its destination. This will be created on the organizations Internet-facing server(s) in order to deliver email. This option is generally used when you do not use a smart host to deliver email.

- Partner: The Partner connector is, unsurprisingly, used to send email to a partner domain. For example, if a one company acquires another, then there may be business requirements that need these two companies to run independently, but they also want to make sure that emails shared between these domains are not sent over the public internet. This is when the partner Send connector comes into effect.

Advise: Smart host will be used as a gateway to send emails to outside world, let exchange take care of all internal emails ;-).

Note: Please award points if you are happy with the answer.

Cheers

ExchangePandit

I might not have been completely clear on my question.
I would like to route only e-mails from one of our internal domains, domain1.com over a specific Send Connector, regardless of which external e-mail address these e-mails are sent to.

E-mails from all other internal domains should be sent out over the standard * Send Connector.
I cannot seem to find this option from your above reply, so this might not be possible at all.

If so, I am just wondering how companies are performing testing when introducing new gateway equipment.

Your question:

I would like to route only e-mails from one of our internal domains, domain1.com over a specific Send Connector, regardless of which external e-mail address these e-mails are sent to.


I guess you have multiple SMTP domains like domain1.com, domain2.com;

Now you want to send emails from domain1.com from one SMTP connector and domain2.com from another, is that correct?

Regards

That is correct.

This is part of my testing to ensure that my new IronPort e-mail gateway is working as it should.
Once my testing is completed, I want to research the possibility of using both my existing and my new e-mail gateway in a load balancing scenario.
I know how to do this for external incoming e-mails (two MX records with different cost), but not sure if something similar is possible from internally to externally?