Re: [Exim] receiver_verify_*

Top Page
Delete this message
Reply to this message
Author: David Corbin
Date:  
To: Greg Ward
CC: exim-users
New-Topics: [Exim] multiple domains driving crazy
Subject: Re: [Exim] receiver_verify_*
----- Original Message -----
From: "Greg Ward" <gward@???>
> On 03 October 2001, David Corbin said:
> > I think that adding:
> >
> >

receiver_verify_addresses=^!((192.168.100.\d{1,3})|(x.y.z.(49|50|51|52|53|54
> > |56|57|58|59|60|61|62|63)))
>
> Ouch! There are some things regexes were not meant to do.



I agree, there are some things RegExs weren't meant to do. But, you live
with the capabilities you've got.

>
> > will match all machines that are not on one of the two following

networks:
> > 192.168.100.0/24 and x.y.z.48/28
> >
> > Does that look right to you? Is there a better way to do this?
>
> There certainly is. How about
>
> receiver_verify_addresses= = !192.168.100.0/24
>


Looks good as far as it goes. Are there really supposed to be two equals
(=) in the above example?

> for a start? The x.y.z.48/24 thing looks really fishy: do you really
> want to allow non-verified sender addresses from any IP address that
> happens to end in 49 .. 63? (If I'm reading that right.)
>


I don't think that's what it does. Althought I didn't *directly* say it,
x.y.z is fix.. Basically, I've get 4 bit subnet that I need to "cover".

My concern with the solution you provide is that saying
"receiver_verify_address=!A:!B" is not logic-wise the same as !(A|B),
which is really what I want.