---------- 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/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. the problem postscreen MX pinging the mysql server on the same switch shows: round-trip min/avg/max/stddev = 0.143/0.227/0.443/0.100 ms 2 non-problem postscreening MXs pinging from South Carolina to Atlanta show: round-trip min/avg/max/stddev = 4.613/4.945/5.249/0.205 ms It's quite confusing to tease where the problem is. ========= btw, what does postscreen send to smtp client when postscreen logs this: egrep -ic "all screening ports busy" /var2/log/maillog 5615 This is on both SC machines postscreen/mysql into ATL, and with postscreen_greet_wait = 2 (which greatly reduced the busy's compared to 10 sec). Len
