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

Help with Exchange 2010 Send Connectors

I have a test Exchange 2010 server setup that I am playing around with.  I have multiple accepted domains setup on the Exchange server, mydomain1.com and mydomain2.com.  

I want to send the outgoing email for mydomain1.com and mydomain2.com via different Send Connectors.  I have set up a send connector my mydomain1.com with the following settings:

Type - SMTP
Address Space - mydomain1.com
Include all subdomains is checked
Cost - 1
Route mail through the following smart hosts is enabled
FQDN for smart host - mail.mydomain1.com
Basic Authentication is enabled with the proper username and password for my web hosting email account.

I set up another Send Connector for mydomain2.com with the same type of configuration.  

However, I cannot get my outgoing mail to send out.  Any thoughts on what I am doing wrong?
0
csimmons1324
Asked:
csimmons1324
  • 4
  • 3
  • 3
1 Solution
 
Exchange_GeekCommented:
Send connector are not for you're local domains - they're for the domains whom you want to send-to NOT send-from.

You got the concepts wrong my friend.

Since, those domains are accepted domains, why would Exchange send emails for those domains externally to internet?

Regards,
Exchange_Geek
0
 
NetfloCommented:
I agree with Exchange_Geek on what you're trying to achieve, I wouldn't worry too much about the identity of the outbound connector.

To get emails to leave, you need select 'Use DNS MX records to route mail automatically' not via a Smart Host. As this essentially leaves your Exchange server confused on where exactly to sent mail out.

Hope this helps.
0
 
csimmons1324Author Commented:
I have a number of various  web sites that I run.  Each of these web domains is setup as an accepted domain on my Exchange server.  I have an AD user account created for each email address that I receive email from.  For example,

- first.last@mydomain1.com
- sales@mydomain2.com

It was my understanding that the smart host is what is used to perform the routing of the outgoing email messages.

I want to route all email from mydomain1.com through my web hosting accounts email server.  I want to route all email from mydomain2.com through the transactional email service Mandrill.

If I put a * in the address space for the Send Connector that I created for routing my messages through Mandrill then all my email from mydomain1.com and mydomain2.com is sent through the Mandrill transactional email service.  

It seems that I am on the right path.  I just cannot figure out how to get one mydomain1.com to send over one smart host and mydomain2.com to send over another.
0
Restore individual SQL databases with ease

Veeam Explorer for Microsoft SQL Server delivers an easy-to-use, wizard-driven interface for restoring your databases from a backup. No expert SQL background required. Web interface provides a complete view of all available SQL databases to simplify the recovery of lost database

 
NetfloCommented:
The star and option for domains is if you want to route traffic for say gmail.com (destination domain) via a send connector - not the other way around.

If you had a two Exchange servers, yes you could do this, with users of one organisation on one server and sending via send connector 1, and users of the other organisation on the second server and sending via send connector 2.

For what you're trying to do on one server, can't be done the way you want to.
0
 
Exchange_GeekCommented:
Let me get facts clear here -

@mydomain1.com and mydomain2.com are you're internal domains? Are these stamped on your users as primary or secondary domains?

If yes, you're send connectors would be needed to be changed from internet to internal-relay to be sent to a smart-host.

If not, explain it better please.

Regards,
Exchange_Geek
0
 
NetfloCommented:
Further reading so you have a clear understanding of how send connectors work: http://technet.microsoft.com/en-us/library/aa998662.aspx
0
 
csimmons1324Author Commented:
I was able to achieve what I wanted to do using the Routing Rule Agent found here - http://routingruleagent.codeplex.com/documentation?version=9
0
 
Exchange_GeekCommented:
whoa whoa whoa hang on my friend, what sounds so sweet and just click click ahead, may cost you very dearly the moment you upgrade to SP2-3-4-5. Understand, what you are doing is a hack and not supported by Microsoft.

Always read the fine print

The project is freeware, open source, but is not supported by Microsoft.

You're keeping the product company at bay, and banking on some third party company solution.

I'd request you NOT to work with such companies and their solution and keep everything else at risk.

Regards,
Exchange_Geek
0
 
NetfloCommented:
I'd recommend not to install this, you'll probably end up breaking your Exchange and remember you need to ensure your server is fully supported in the eyes of MS in order for them or EE to help you. I would take that on-board that you have two Exchange experts advising you against this.

One thing to ask, is the send connector really that important, as its just used as the FQDN for SMTP transmission. If anything I doubt you're sending and receiving via multiple IPs with rDNS records set either?

Typically in your scenario you would have an independent domain, used for sending emails and receiving emails, for example: hostingSMTP.com. That way you can keep adding the domains and ensure you don't need to keep tinkering with send connectors or editing DLLs. You have a consistent MX records setup and rDNS set for all your sending domans.

Keep it simple and supported, you'll be a happy man in the long run.
0
 
csimmons1324Author Commented:
I am accepting my own solution due to the fact that nobody was able to provide an answer on how to achieve what I was looking to do.  While advised not to use the solution that I proposed it works for my situation.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

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