none
Redirect specific email to different smtp host

    Question

  • Hello,

    I need to be able to redirect email sent to our support email address support@domain.com to a different email server than what we are using for everything else.  We have a hosted ticketing system that needs to get email sent to our domain to it's SMTP server.   Should this be done with MX records?  or should our Exchange Server handle this ?

    Monday, November 04, 2013 8:44 PM

Answers

  • I can't think of any way you could realistically do that via MX records, since you're going to need to have all mail for domain.com going to one place or the other, and MX records can't differentiate over the email alias used (though if you were using something like support@support.domain.com them it'd be a different matter).

    Two ways I can think of that you could do this.

    1) If the hosted ticketing system email address is able to have multiple email aliases, as well as it being configured with support@domain.com as the default address, also configure a dummy alias using a different domain, perhaps even support@support.domain.com. Configure the MX records for that dummy domain to point to the ticketing system's SMTP server. Then in your Exchange setup configure support@domain.com to forward to the dummy address. Exchange can then receive the message along with all other messages for your domain, forward it to the required destination, and obviously when replies are sent from the ticketing system they'll still be going from support@domain.com since as far as the remote system is concerned it's local to itself.

    2) Within your organisation configuration, setup a send connector for *.domain.com and configure it to route mail to the ticketing system's SMTP server as the smart host. Any messages received by Exchange for valid aliases will be delivered locally (eg won't use the send connector), but those aliases not handled by exchange, specifically support@ will be routed to the remote system and will arrive in the ticketing system. Of course this does mean that any other mail that would receive an NDR from Exchange will be routed onwards, so the NDR will come from the ticket system server instead, so you'd have to decide how much of an issue that would be for you, and how much control you have over that remote system.

    • Marked as answer by Mike BG Monday, November 04, 2013 11:25 PM
    Monday, November 04, 2013 9:19 PM

All replies

  • I can't think of any way you could realistically do that via MX records, since you're going to need to have all mail for domain.com going to one place or the other, and MX records can't differentiate over the email alias used (though if you were using something like support@support.domain.com them it'd be a different matter).

    Two ways I can think of that you could do this.

    1) If the hosted ticketing system email address is able to have multiple email aliases, as well as it being configured with support@domain.com as the default address, also configure a dummy alias using a different domain, perhaps even support@support.domain.com. Configure the MX records for that dummy domain to point to the ticketing system's SMTP server. Then in your Exchange setup configure support@domain.com to forward to the dummy address. Exchange can then receive the message along with all other messages for your domain, forward it to the required destination, and obviously when replies are sent from the ticketing system they'll still be going from support@domain.com since as far as the remote system is concerned it's local to itself.

    2) Within your organisation configuration, setup a send connector for *.domain.com and configure it to route mail to the ticketing system's SMTP server as the smart host. Any messages received by Exchange for valid aliases will be delivered locally (eg won't use the send connector), but those aliases not handled by exchange, specifically support@ will be routed to the remote system and will arrive in the ticketing system. Of course this does mean that any other mail that would receive an NDR from Exchange will be routed onwards, so the NDR will come from the ticket system server instead, so you'd have to decide how much of an issue that would be for you, and how much control you have over that remote system.

    • Marked as answer by Mike BG Monday, November 04, 2013 11:25 PM
    Monday, November 04, 2013 9:19 PM
  • Thanks Keith,

    That confirms what I was thinking.  Seems the subdomain option would work the best for our setup. 

    Also we're kicking around the idea of having a new mailbox with rules to forward then delete all incoming mail.  Then it would pass through our spam filters before forwarding and we would be able to have a transaction log on our exchange box in case there was a delivery issue.

    Monday, November 04, 2013 11:29 PM