Len Conrad:
> -- Original Message --
> From: wie...@porcupine.org (Wietse Venema)
> Date: Fri, 4 Dec 2009 14:13:17 -0500 (EST)
> >I'll mkae a note that postscreen must be used only with low-latency databases
> >such as local files.
>
> the problem postscree
-- Original Message --
From: wie...@porcupine.org (Wietse Venema)
Date: Fri, 4 Dec 2009 14:13:17 -0500 (EST)
>Len Conrad:
>> I've got more data. The killer option is when I have this on:
>>
>> postscreen_blacklist_networks =
>> mysql:/usr/local/etc/postf
Len Conrad:
> I've got more data. The killer option is when I have this on:
>
> postscreen_blacklist_networks =
> mysql:/usr/local/etc/postfix/mysql-mta_clients_reactive_b.cf
I'll mkae a note that postscreen must be used only with low-latency databases
such as local files.
Wietse
>> freebsd 7.2
>> mail_version = 2.7-20091008
>>
>> out of 6 postscreen machines, I've got one that every 20 or 30
>> minutes just halts, port 25 is dead (several monit agents see it
>> dead), then it starts off by itself after a few minutes, dumping
>> a bunch of these in maillog:
>>
>> warning
Len Conrad:
> freebsd 7.2
> mail_version = 2.7-20091008
>
> out of 6 postscreen machines, I've got one that every 20 or 30
> minutes just halts, port 25 is dead (several monit agents see it
> dead), then it starts off by itself after a few minutes, dumping
> a bunch of these in maillog:
>
> warni
freebsd 7.2
mail_version = 2.7-20091008
out of 6 postscreen machines, I've got one that every 20 or 30 minutes just
halts, port 25 is dead (several monit agents see it dead), then it starts off
by itself after a few minutes, dumping a bunch of these in maillog:
warning: postscreen_dnsbl_query:
