Sorry - I should have said: Postfix 2.11.3, running on Debian Jessie.
Also, I ran these tests using postmap when it became apparent to me that postfix itself was not matching address prefixes in hash tables. On 14/05/2018 11:18, jack wrote: > Hi, > > In the online documentation for access tables > (http://www.postfix.org/access.5.html), it says: > > Subnetworks are matched by repeatedly truncating > the last ".octet" from the remote IPv4 host address > string until a match is found in the access table, or > until further truncation is not possible. > > This is supposedly subject only to the restriction that the table is an > indexed file "such as DB or DBM". > > I have the following client_access table: > 5.188.9 REJECT WebShield Network trying to hack Dovecot > 2018-05-10 - test > 5.188.9.1 REJECT WebShield Network trying to hack Dovecot 2018-05-10 > > I compile the table to create client_access.db: > # postmap client_access > > I then try: > # postmap -q 5.188.9.2 client_access > [no output] > > # postmap -q 5.188.9.1 client_access > REJECT WebShield Network trying to hack Dovecot 2018-05-10 > > The behaviour of postmap seems to be at odds with the documentation; > specfically, it does not seem to be possible to match an address against > an address-prefix in the table. Am I misunderstanding the docs, or do > they need fixing? > > I haven't tried any of the other indexed lookup types; is there some > other table type that works properly? Do I need to test them all to see > if they comply with the docs? > > Thanks, >
