I do use: "... BLACKLIST_HELO=1 BLACKLIST_NETBLOCK=1 AUTO_BLACK_LISTING=1 HELO_CHECK=1 HELO_MAX_COUNT=10 HELO_BLACKLIST_AUTO_EXPIRE=0 HELO_AUTO_EXPIRE=0 ..." in my policyd.conf.
There is a localhost entry in my blacklist_helo table: mysql> select * from blacklist_helo where _helo='localhost'; +-----------+ | _helo | +-----------+ | localhost | +-----------+ 1 row in set (0,00 sec) When I check my blacklist I wonder why there seem to be three different types of autoblacklisted helos. mysql> select * from blacklist where _description like '%localhost%'; .... | 222.253.21.103. | # blacklisted helo: (localhost) | 0 | | 222.252.232.6.% | # blacklisted helo: (localhost) | 0 | | 222.252.246.175 | # blacklisted helo: (localhost) | 0 | .... Well I would expect just to see entries ending with '.%', because I have set BLACKLIST_NETBLOCK=1. Does anybody have an explanation for the single-host- and single-host-with-a-dot-at-the-end-notation ? I did not touch the source of policyd and use: policyd 1.81 postfix-2.4.3 mysql-4.1.22 Linux version 2.4.20-19.8 Red Hat Linux 8.0 3.2-7 gcc version 3.2 viele Grüße, Tom Neubauer ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ policyd-users mailing list policyd-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/policyd-users
