Re: [Exim] BUG? ignore_target_hosts broken with @mx_any

Góra strony
Delete this message
Reply to this message
Autor: Philip Hazel
Data:  
Dla: Peter A. Savitch
Temat: Re: [Exim] BUG? ignore_target_hosts broken with @mx_any
On Wed, 5 Feb 2003, Peter A. Savitch wrote:

> DNS lookup of hubbardcollege.org (MX) succeeded
> discarded duplicate host dns1.pixelgate.net (MX=40)
> Configured local interface: address=127.0.0.1
> Configured local interface: address=217.xxx.xxx.xxx
> local host in host list - removed hosts:               <=============
>   mail.pixelgate.com 127.0.0.1 30
> host_find_bydns yield = HOST_FOUND (2); returned hosts:
>   mail.hubbardcollege.org 209.239.252.199 10
>   dns1.pixelgate.net 66.254.66.99 20
> hubbardcollege.org in "!@mx_any"? no (matched "!@mx_any")


It's a matter of ordering. The rule for removing the local host as a
secondary MX has been applied before any tests for ignore_target_hosts.

> At least, ignore_target_hosts is ALWAYS NULL as it's always passed as
> NULL argument.
>
>      at src/host.c(2060), function host_find_bydns()
>  ... called from match.c(192), function check_string()
>  ... called from match.c(573), function match_check_list()
>  ... called from match.c(757), function match_isinlist()
>  ... called from route.c(424), function route_check_dls()
>  ... called from route.c(775), function check_router_conditions()

>
> How to pass ignore_target_hosts to host_find_bydns() through all of
> these ? Any workarounds? Still, I'm not sure it will help to kick off
> broken MX records out in this way.


The problem is that ignore_target_hosts is an option of the dnslookup
router. You are not using the dnslookup router when processing a host
list. Consequently, there is no facility for passing such information
when MX records are looked up in a host list by @mx_any.

--
Philip Hazel            University of Cambridge Computing Service,
ph10@???      Cambridge, England. Phone: +44 1223 334714.