---------- Original Message ---------------------------------- From: Ralf Hildebrandt <ralf.hildebra...@charite.de> Reply-To: postfix-users@postfix.org Date: Fri, 1 May 2009 20:56:15 +0200
>* Len Conrad <lcon...@go2france.com>: >> postmap -q "67.218.188" >> mysql:/usr/local/etc/postfix/mysql-mta_clients_reactive_b.cf >> 554 mta_client_reactive_b >> >> postmap -q "67.218.188.4" >> mysql:/usr/local/etc/postfix/mysql-mta_clients_reactive_b.cf >> ... no data >> >> man 5 access seems to make no distinction between .map and SQL tables: >> >> HOST NAME/ADDRESS PATTERNS >> >> With lookups from indexed files such as DB or DBM, or from networked >> tables such as NIS, LDAP or SQL, the following lookup patterns are >> examined in the order as listed >> >> 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. > >So where is the problem now? 1. my email client discarded my wonderful Subject: line 2. The problem is that a query for 67.218.188.4 is not matched by an entry of 67.218.188. This works in hash:.map tables, so why doesn't it work in SQL tables? iow, how to block a Class C with SQL table? Len
