On Wed, 22 Apr 2009 17:27:18 -0400, mbneto <mbneto@???> wrote:
> The domain.com is simply an example. Not the real one.
example.com, example.net, example.org - all standard example domains
already reserved in the domain space for such purposes.
> I am hoping that there is a flag somewhere I can disable so exim will
> ignore
> this or maybe a tweak in the configuration.
>
> I've tried the manualroute without luck. I add the following as the
first
> router
>
> problemdomain:
> driver = manualroute
> domains = domain.com
> transport = remote_smtp
> route_list = IP.of.the.MX
>
> But it is not working.
Your manual router should have worked. Did you place it before your normal
domains one? Did you restart exim?
And then slightly more directed at the offending mail server/DNS admin ....
There's no simple flag for this one as it's completely broken. This would
be akin to someone putting an IP address in an MX record - it's simply
broken and not allowed since it breaks too many systems. In this case you
should educate the offending server administrator on what is allowed in
hostnames. The "_" is not as it is a special character used to seperate
hostname DNS space and different protocols stored in DNS (eg _domainkeys,
_kerberos._tcp.dc._msdcs, _ldap._tcp.pdc._msdcs). The "_" allows these
other bits of information to sit side by side in a zone file and not
collide. As such, the MX record this example domain is giving is in fact
not inside hostname space. Just because it can be added to a zone file
doesn't mean it should - There's 3 lights on a traffic light but you only
drive through it when it's green.
--
The Exim Manual
http://www.exim.org/docs.html
http://docs.exim.org/current/
