On Wed, 28 May 2003, Kai Risku wrote:
> It seems like hosts_treat_as_local is not able to reference
> named lists correctly, because I tried to be smart in
> our Exim 4.12 setup and set:
>
> hosts_treat_as_local = +local_domains
>
> referencing the domain list which includes some virtual
> domains and wildcard patterns. This resulted in a problem
> where the exim server was a secondary MX and the primary
> MX was down (it continuously delivered the mail to itself
> until it detected the loop and bounced the mail).
>
> When setting the same domainlist directly as an argument
> to hosts_treat_as_local everything worked properly.
>
> Is this a bug or simply undocumented behaviour?
A. Could it be this bug, which is fixed in 4.20?
7. If a domain list contained @mx_any, or @mx_secondary, and the DNS contained
secondary MX records for a domain, but all the other MX (higher priority)
records pointed to non-existent hosts, Exim was behaving as if the domain
did not match the list item. This has been fixed.
That doesn't sound very likely, given that inserting the domain list
directly worked, but you never know.
B. If not, please provide some -d debugging output that shows the
problem. You should be able to generate this using -d -bt.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book: http://www.uit.co.uk/exim-book
