On Sun, Dec 16, 2007 at 11:05:29PM +0000, Enrico Zini wrote: > Package: whitelister > Version: 0.8-4 > Severity: normal > > Hello, > > Thanks for maintaining whitelister.
actually I'm also upstream :P > I sometimes found something like this in my logcheck reports: > > Dec 16 16:39:32 xxxx postfix/smtpd[7546]: warning: connect to > private/whitelister.ctl: Resource temporarily unavailable > Dec 16 16:39:32 xxxx postfix/smtpd[7546]: warning: problem talking to server > private/whitelister.ctl: Resource temporarily unavailable > Dec 16 16:39:32 xxxx postfix/smtpd[7542]: warning: connect to > private/whitelister.ctl: Resource temporarily unavailable > Dec 16 16:39:32 xxxx postfix/smtpd[7542]: warning: problem talking to server > private/whitelister.ctl: Resource temporarily unavailable > Dec 16 16:39:33 xxxx postfix/smtpd[7542]: warning: connect to > private/whitelister.ctl: Resource temporarily unavailable > Dec 16 16:39:33 xxxx postfix/smtpd[7542]: warning: problem talking to server > private/whitelister.ctl: Resource temporarily unavailable > Dec 16 16:39:33 xxxx postfix/smtpd[7542]: NOQUEUE: reject: RCPT from > xxxxxx.xxxxxx.xx[xx.xx.xx.xx]: 451 4.3.5 Server configuration problem; > from=<[EMAIL PROTECTED]> to=<[EMAIL PROTECTED]> proto=SMTP > helo=<xxxxxx.xxxxxx.xx> > > If I go and do a ps, I see that there are whitelister processes around, > and indeed mail is still generally received, except these few sporadic > cases. yeah, I believe this even has already been reported, anyways, it's because for some reason the "fork/exec" is too slow, and postfix timeouts. It's hard to reproduce, and I kind of abandonned whitelister as upstream, and is working on a replacement of it in C. Note that when it "fails" this way, postfix falls back to the next measure, which usually is greylist, so it generates delay, but won't let you lose any mail. Sorry for the inconvenience. -- ·O· Pierre Habouzit ··O [EMAIL PROTECTED] OOO http://www.madism.org
pgpOIiUOj1YLm.pgp
Description: PGP signature
