Re: [Exim] @mx_any and 127.0.0.1

[2004-04-15] Dean Brooks wrote:
> Simply removing ALL the MX records completely, and then blocking
> inbound SMTP on port 25 of the underlying A record completely
> solves the problem.

In the cases where the A address points to a shared "virtual host"
IP address which happens to be running an smtpd for other domains...

Using 127.0.0.1 as an MX for domains that receive mail is especially
stupid since mail will most likely be bounced rather than queued
in the event of a temporary network problem located toward the sender end.

Since there's no real way of measuring the effectiveness of bogus MX
records as an anti-spam measure, I'd advise they not be used. But
if people *must* use a non-deliverable IP address I would use an
address within 192.0.2.0/24 (TEST-NET) which should not be found
on either public or private networks.

--
Lee Maguire <lee@???>