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

This appears to happen during periods of load, but also when the server is
idle. I understand it's possible to increase the timeout, but I would think
10s would be long enough, so didn't want to start doing that. This is also
on multiple hosts on multiple different, unrelated networks.

I'm also using a half-dozen RBLs, but they don't all always timeout.

I'm using a local bind caching server on the hosts that are involved.
Should I consider setting up rbldnsd for this instead? Or is that only for
caching local RBLs only?

What is the result of this timeout? Does postscreen/dnsblog retry, or is
the attempt failed and the mail just passed on?

Here is the relevant postscreen info from my config. Please let me know if
the full config is necessary.

postscreen_access_list = permit_mynetworks,
cidr:/etc/postfix/postscreen_access.cidr
postscreen_blacklist_action = drop
postscreen_dnsbl_action = enforce
postscreen_dnsbl_reply_map =
pcre:$config_directory/postscreen_dnsbl_reply_map.pcre
postscreen_dnsbl_sites = mykey.zen.dq.spamhaus.net*3 b.barracudacentral.org*2
bl.spameatingmonkey.net*2 bl.spamcop.net dnsbl.sorbs.net psbl.surriel.com
bl.mailspike.net 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
postscreen_dnsbl_threshold = 3
postscreen_greet_action = enforce
postscreen_whitelist_interfaces = static:all 172.XX.YY.160/32 64.XX.YY.0/24
67.XX.YY.0/24

Thanks so much,
Alex

Reply via email to