On Fri, Aug 16, 2013 at 2:49 AM, Paul Walsh <Paul.Walsh@???> wrote:
>
> acl_smtp_rcpt I have the following:
> accept hosts = +relay_hosts
> #
> # If we've got this far it means the source and recipient are outside
> our control
> # and thus someone is trying to use us as a relay.
> #
> deny message = relay not permitted
> This is all fine and dandy until the entry for one of the hosts in
> relay_hosts is deleted from DNS. As Exim works its way through the
> list to verify if a sending host is allowed to relay mail, it hits the
> entry for the now defunct host, tries a forward DNS lookup to get an
> IP address to compare with that of the sending host and, because the
> lookup fails, immediately considers the sending host to not be in the
> list thus causing delivery to fail with the "relay not permitted"
> message. Unfortunately, any attempt to relay mail by a host in the
> list after the defunct host also results in a "relay not permitted"
> rejection.
> I'm trying to determine if it's possible to have Exim parse the entire
> list, only rejecting if the sending IP address didn't match any of
> those returned by looking up each host, or at the very least flag up
> some sort of warning that the host list contains addresses that can't
> be resolved.
> Thoughts?
Read all three messages in this thread:
https://lists.exim.org/lurker/message/20130816.094929.4afff885.hu.html
...Todd
--
The total budget at all receivers for solving senders' problems is $0.
If you want them to accept your mail and manage it the way you want,
send it the way the spec says to. --John Levine
