Hello list, we have an intermittent problem here. We saw several times that postfix starts (temporarily) bouncing mails with "450 server configuration error". All we see in our logs is
Nov 14 00:22:54 XXXX postfix/smtpd[5456]: connect from pool-68-237-243-52.ny325.east.verizon.net[68.237.243.52] Nov 14 00:24:37 XXXX postfix/smtpd[5456]: warning: timeout on 127.0.0.1:12525 while reading input attribute name Nov 14 00:24:37 XXXX postfix/smtpd[5456]: warning: problem talking to server 127.0.0.1:12525: Connection timed out Nov 14 00:26:18 XXXX postfix/smtpd[5456]: NOQUEUE: reject: RCPT from pool-68-237-243-52.ny325.east.verizon.net[68.237.243.52]: 450 Server configuration problem; from=<[EMAIL PROTECTED]> to=<[EMAIL PROTECTED]> proto=ESMTP helo=<friend> Until now, we suspected either linux limits (number of filehandles etc.), or a too small number of $MAX_PROC for policyd-weight - without having any evidence. This changed today. We experienced severe performance problems with the DNS server, which acts as forwarder for our caching only bind9 on our machine. One sideeffect of those performance problems was exactly the error described above - until those issues were resolved, all mails were bounced with the 450 error. It would be my understanding that in case of DNS errors policyd-weight should return DUNNO after $MAXDNSERR queries, right? Any ideas on this? Anything we could do to debug this? We are using 0.1.13 beta-16 on SLES, started in daemon mode, with the following config: $TCP_PORT = 12525; $LOCKPATH = '/var/tmp/.policyd-weight/'; $dnsbl_checks_only = 1; $VERBOSE = 0; $MIN_PROC = 20; $MAX_PROC = 200; Note: $MAX_PROC matches the number of smtpd processes in master.cf. Thanks in advance U. P.S. I had to copy/paste this message again to send to this list - I hope there are no funny artefacts from this process this time :) ____________________________________________________________ Policyd-weight Mailinglist - http://www.policyd-weight.org/
