Re: Understanding postscreen timeouts

2014-05-02 Thread /dev/rob0
On Fri, May 02, 2014 at 08:10:18PM -0400, Alex wrote: > On Fri, May 2, 2014 at 6:45 PM, Stan Hoeppner > wrote: > > On 5/2/2014 6:07 AM, Wietse Venema wrote: > > > Stan Hoeppner: > > >>> swl.spamhaus.org*-4 > > >>> list.dnswl.org=127.[0..255].[0..255].0*-2 > > >>> list.dnswl

Re: Understanding postscreen timeouts

2014-05-02 Thread Alex
Hi, On Fri, May 2, 2014 at 6:45 PM, Stan Hoeppner wrote: > On 5/2/2014 6:07 AM, Wietse Venema wrote: > > Stan Hoeppner: > >>> swl.spamhaus.org*-4 > >>> list.dnswl.org=127.[0..255].[0..255].0*-2 > >>> list.dnswl.org=127.[0..255].[0..255].1*-3 > >>> list.dnswl.org=12

Re: Understanding postscreen timeouts

2014-05-02 Thread Stan Hoeppner
On 5/2/2014 6:07 AM, Wietse Venema wrote: > Stan Hoeppner: >>> swl.spamhaus.org*-4 >>> list.dnswl.org=127.[0..255].[0..255].0*-2 >>> list.dnswl.org=127.[0..255].[0..255].1*-3 >>> list.dnswl.org=127.[0..255].[0..255].[2..255]*-4 >> >> Consolidate these last 3 to somet

postscreen_dnsbl_timeout parameter (was: Understanding postscreen timeouts)

2014-05-02 Thread Wietse Venema
Wietse Venema: > Alex: > > I'm using postfix-2.10.3 with fedora20 and have configured postscreen with > > spamhaus, barracuda, and a few other DNSBLs. I'm however occasionally > > receiving the following timeout message: > > > > May 1 17:15:01 mail01 postfix/postscreen[4429]: warning: dnsblog rep

Re: Understanding postscreen timeouts

2014-05-02 Thread Wietse Venema
Stan Hoeppner: > > swl.spamhaus.org*-4 > > list.dnswl.org=127.[0..255].[0..255].0*-2 > > list.dnswl.org=127.[0..255].[0..255].1*-3 > > list.dnswl.org=127.[0..255].[0..255].[2..255]*-4 > > Consolidate these last 3 to something like: > list.dnswl.org=127.0.[2..1

Re: Understanding postscreen timeouts

2014-05-02 Thread Tom Hendrikx
On 05/02/2014 03:15 AM, Alex wrote: > Hi, > > On Thu, May 1, 2014 at 5:38 PM, Wietse Venema > wrote: > > Alex: > > I'm using postfix-2.10.3 with fedora20 and have configured > postscreen with > > spamhaus, barracuda, and a few other DNSBLs. I'm howeve

Re: Understanding postscreen timeouts

2014-05-01 Thread Stan Hoeppner
On 5/1/2014 8:15 PM, Alex wrote: ... > These are both corporate 10mbs dedicated links and I don't think latency > and/or bandwidth is a problem. The problem, if network related, will be UDP packet loss somewhere in the end-to-end path, not b/w or latency on the CPE link into the provider's net. >

Re: Understanding postscreen timeouts

2014-05-01 Thread Alex
Hi, On Thu, May 1, 2014 at 5:38 PM, Wietse Venema wrote: > Alex: > > I'm using postfix-2.10.3 with fedora20 and have configured postscreen > with > > spamhaus, barracuda, and a few other DNSBLs. I'm however occasionally > > receiving the following timeout message: > > > > May 1 17:15:01 mail01

Re: Understanding postscreen timeouts

2014-05-01 Thread Wietse Venema
Alex: > I'm using postfix-2.10.3 with fedora20 and have configured postscreen with > spamhaus, barracuda, and a few other DNSBLs. I'm however occasionally > receiving the following timeout message: > > May 1 17:15:01 mail01 postfix/postscreen[4429]: warning: dnsblog reply > timeout 10s for swl.sp

Understanding postscreen timeouts

2014-05-01 Thread Alex
Hi, I'm using postfix-2.10.3 with fedora20 and have configured postscreen with spamhaus, barracuda, and a few other DNSBLs. I'm however occasionally receiving the following timeout message: May 1 17:15:01 mail01 postfix/postscreen[4429]: warning: dnsblog reply timeout 10s for swl.spamhaus.org T