Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an issue due to "split DNS vision" where email is generated at a host and sent via a smarthost (relay) to an external system out of my control (business partner).

The generating server has access to the remote domain's internal DNS and do not see an MX record for the particular domain name (, but resolves a CNAME instead ( CNAME, resolves an MX record listed for the CNAME target ( IN MX 10, and passes the email on to the smarthost.

The smarthost which has the "external" view of the remote system's DNS zone where does have a MX record ( IN MX 10 tries to deliver the email by looking for the MX for, fails and rejects the email.

  • The business partner could publish a MX record in his internal DNS view for, so my server won't do the CNAME expansion, and passing the mails to the smarthost without changing to

  • I could configure the generating sendmail to not do CNAME expansion by setting confDONT_EXPAND_CNAMES ( docs), but this might have unforeseen effects for other domains.

    Is there a way to do this for only emails?

share|improve this question

migrated from Dec 8 '11 at 14:36

This question came from our site for computer enthusiasts and power users.

up vote 1 down vote accepted


R$+ <@ sub . example . com . > $*      $#smtp $@ [ ] $: $1 < @ . > $2
share|improve this answer
In the end I added the following to the Canonify2 rule, after the part where DNS resolution is made: R$+ <@ sub . example . com . > $* $: $1 < @ . > $2 Seems to give the wanted result in testing. Thank you very much for the suggestion! – sajb Dec 9 '11 at 8:06

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.