Re: postscreen blacklist painful refresh

2012-05-23 Thread DTNX Postmaster
On May 23, 2012, at 15:35, Wietse Venema wrote: > Wietse Venema: >> Wietse Venema: >>> Maciej Uhlig: We run fail2ban to update postscreen blacklist which is cidr file. To make postscreen see the changes we have to reload postfix. Yesterday we found postfix was reloaded more than 300

Re: postscreen blacklist painful refresh

2012-05-23 Thread Wietse Venema
Wietse Venema: > Wietse Venema: > > Maciej Uhlig: > > > We run fail2ban to update postscreen blacklist which is cidr file. To > > > make postscreen see the changes we have to reload postfix. Yesterday we > > > found postfix was reloaded more than 3000 times. Sure it is not > > > acceptable. > > >

Re: postscreen blacklist painful refresh

2012-05-23 Thread DTNX Postmaster
On May 23, 2012, at 11:23, Maciej Uhlig wrote: > We run fail2ban to update postscreen blacklist which is cidr file. To > make postscreen see the changes we have to reload postfix. Yesterday we > found postfix was reloaded more than 3000 times. Sure it is not acceptable. > > What would be the best

Re: postscreen blacklist painful refresh

2012-05-23 Thread Wietse Venema
Wietse Venema: > Maciej Uhlig: > > We run fail2ban to update postscreen blacklist which is cidr file. To > > make postscreen see the changes we have to reload postfix. Yesterday we > > found postfix was reloaded more than 3000 times. Sure it is not acceptable. > > Surely you don't have to reload i

Re: postscreen blacklist painful refresh

2012-05-23 Thread Wietse Venema
Maciej Uhlig: > We run fail2ban to update postscreen blacklist which is cidr file. To > make postscreen see the changes we have to reload postfix. Yesterday we > found postfix was reloaded more than 3000 times. Sure it is not acceptable. Surely you don't have to reload it EVERY 30 SECONDS. What ab

Re: postscreen blacklist painful refresh

2012-05-23 Thread Jean-Michel Bruenn
I'd let fail2ban write to a temporary file / cidr file which you move by cronjob all 10 minutes if there has been a change (shasum). That way your blacklist will updated at maximum all 10 minutes (or whatever delay you define) and _only_ if there has been a change. though 3000 times would mean ci

postscreen blacklist painful refresh

2012-05-23 Thread Maciej Uhlig
We run fail2ban to update postscreen blacklist which is cidr file. To make postscreen see the changes we have to reload postfix. Yesterday we found postfix was reloaded more than 3000 times. Sure it is not acceptable. What would be the best way to refresh postscreen blacklist (something like kill