On 2010-11-05 01:38:37 +0100, Jeroen Geilman wrote:
> *REGULAR EXPRESSION TABLES*
> This section describes how the table lookups change when
> the table is given in the form of regular expressions. For
> a description of regular expression lookup table syntax,
> see*regexp_table*(5) <http://www.postfix.org/regexp_table.5.html>
> or*pcre_table*(5) <http://www.postfix.org/pcre_table.5.html>.
>
> Each pattern is a regular expression that is applied to
> the entire string being looked up. Depending on the appli-
> cation, that string is an entire client hostname, an
> entire client IP address, or an entire mail address. Thus,
> no parent domain or parent network search is done,
> /u...@domain/ mail addresses are not broken up into their
> /user@/ and/domain/ constituent parts, nor is/user+foo/ broken
> up into/user/ and/foo/.
>
> Patterns are applied in the order as specified in the ta-
> ble, until a pattern is found that matches the search
> string.
>
> Actions are the same as with indexed file lookups, with
> the additional feature that parenthesized substrings from
> the pattern can be interpolated as*$1*,*$2* and so on.
>
>
> I copied the entire section detailing PCRE access matches for you,
> since you seem unable to find it.
Useless answer. If you had read my message, you would have seen that
I quoted from it.
> How many domain names look like IP addresses to you ?
>
> If check_client_access matches against both IPs and hostnames, then your
> regex table will match against both IPs and hostnames.
This is not what the documentation says:
Depending on the application, that string is an entire client
hostname, an entire client IP address, or an entire mail address.
^^
It is said "or", and "or" doesn't mean "both". Quite the opposite.
--
Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)
