----- Original Message -----
From: "Philip Hazel" <ph10@???>
To: "David Corbin" <dcorbin@???>
Cc: "Greg Ward" <gward@???>; <exim-users@???>
Sent: Thursday, October 04, 2001 11:38 AM
Subject: Re: [Exim] receiver_verify_*
> On Thu, 4 Oct 2001, David Corbin wrote:
>
> > > receiver_verify_addresses = !192.168.100.0/24 : !30.40.50.48/28
> >
> > But *ANY* address will fail one of those two conditions. That's my
point
> > when I say that exim allows me to say (!A or !B), but I don't think it
> > allows (!A and !B)
>
> Consider the address 127.0.0.1. Exim scans the list from left to right.
> It does not match 192.168.100.0/24, so the scan passes on. It does not
> match !30.40.50.48/28 so the scan passes on. Oops, we hit the end of the
> list. The rule in Exim is that if you hit the end of a list after a
> negative item, the answer is "yes". So the answer will be "yes,
> 127.0.0.1 matches this list".
but it DOES match "!192.168.100.0/24".
>
> The reason it works like this is so that simple settings like
>
> receiver_unqualified_hosts = !1.2.3.4
>
> have a natural interpretation.
>
> However, this is never going to work for you. The option
> receiver_verify_addresses is an *address* list (surprise, surprise), not
> a host list. You should really be using receiver_verify_hosts.
>
why? I want to deal with addresses, not hosts.
> > I did RTFM.
>
> You can never RTFM enough. :-)
>
> --
> Philip Hazel University of Cambridge Computing Service,
> ph10@??? Cambridge, England. Phone: +44 1223 334714.
>
>
>
