Author: Eli Sand Date: To: 'exim users' Subject: Re: [exim] MX name with _ : all relevant MX records point to
non-existent hosts
> The domain.com is simply an example. Not the real one.
Careful, you're probably gonna catch flak for that one. There's no reason
to hide the offending domain from us, especially if you're seeking help
relating to said domain.
> I am hoping that there is a flag somewhere I can disable so exim will
> ignore this or maybe a tweak in the configuration.
It's been a while since I read the RFCs, but I'm leaning towards a simple
"sorry, _ is quite simply NOT ALLOWED in a hostname". I would instantly
dismiss a "it works for everyone else", because that's not true.
If it is Exim (it may be in your DNS resolver) that is refusing to
acknowledge that hostname, you may just be out of luck - some rules just
simply should not be bent around/over/under. If that admin refuses to
follow the RFCs, it's his (and his users') loss.
Situations like these can usually be corrected by getting your users to do a
bit of legwork - have them call or somehow contact the intended recipients
and tell them that they can't send email to them because their DNS is broken
(or so their admin, being you, says - point to a relevant RFC if you must).
This should quickly get the recipient contacting their admin and complaining
which results in them either contacting you (and you can seem like the
smarter one by telling them the RFC he's violating), or just fixing the
problem by changing the hostname to something valid.
