On 7/13/2012 10:15 AM, Michael Orlitzky wrote: > We got hit by an iContact run last night and I woke up with several > hundred postmaster messages reporting a queue file write error. We run a > before-queue amavis. > > Here are the logs of one of these transactions: > > Jul 13 10:39:10 mx1 postfix/smtpd[14918]: connect from > drone074.ral.icpbounce.com[216.27.86.131] > > Jul 13 10:39:10 mx1 postfix/smtpd[14918]: discarding EHLO keywords: > DSN > > Jul 13 10:39:10 mx1 postfix/smtpd[14918]: NOQUEUE: > client=drone074.ral.icpbounce.com[216.27.86.131] > > Jul 13 10:40:51 mx1 postfix/smtpd[14918]: warning: timeout talking to > proxy localhost:10024 ... > smtpd pass - - n - 100 smtpd ... > # > # amavisd daemon config > # > > $max_servers = 100; > $max_requests = 25; > $child_timeout = 180; > $smtpd_timeout = 120; >
I suspect 100 smtpd/amavisd processes is way too many for your hardware, preventing amavisd from responding before a timeout occurs. Reduce smtpd process count and amavisd $max_servers until you stop having timeouts. Typical values are 3 to 10 times the number of CPUs you have, and enough RAM to support them with no swapping. -- Noel Jones
