You could always just allow their mail to bounce, and if your users
want to know why they can't mail to that domain - tell them them why
("because the sysadmin at that site has their system misconfigured"),
and give them the email address/phone number of the faulty sysadmin.
You might want to make sure you first send an email to the admin giving
them the specific details of what is misconfigured, with appropriate
RFC reference, since your users wont necesarrily be able to provide
that information.
On Sat, 29 Jul 2000, MikeF wrote:
> Philip Hazel wrote:
> >
> >
> > But note that this is provided just to get people off my back when they
> > are desperate, and to counter the argument "Another MTA allows it; why
> > can't Exim?".
>
> Ha ha ha ha!
> Why do they always say that? ;)
>
> >
> > I do not recommend using this option. Setting MX records to point to IP
> > addresses is Evil and against what the RFC says.
> >
>
> How can I detect this with a filter? I want to bug the hell out of
> the mail admin that does this stupid thing, but still deliver to their
> domain.
>
> It'll say something like what the error says to me "It looks like you
> have an IP address in your MX record on $domain. Please read $url"
>
> And $url will be a page on exim.org (hopefully) that will contain the
> needed parts of the RFCs and a few paragraphs to explain what they
> mean.
>
> Maybe this can be put in the default config file (commented out, of
> course but there still for the exim admin that wants to do so.)?
>
> Mike
>
> --
> ## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##
>
--
