Steve Prior wrote:
I'm just switching to using spamd -m10 (and other opts) from spamc from procmail from sendmail and am wondering what happens when spamd hits the limit and spamc
can't connect to it. Does this get all the ay back through sendmail so the
sender knows that transmission failed? I'm wondering if this means that during
times when I'm getting hit by lots of spam traffic that this will work a little
like greylisting where all email will get an error, but probably only legit
email will try again to get through when the storm is over. Since these storms
typically come when I wouldn't be getting legit email, if this works it would
affect how I tune the -m parameter.
Hi,
In our case we are running spamd on a separate machine (FreeBSD) and the perl connector by default will queue up to 128 processes when connecting in TCP mode.
Since we run with a max of 120 connections with qmail plus -m 10 for spamd, all mail will get scanned via SA.
I'm not sure how the unix sockets work, but tcp sockets will queue a backlog.
How this all may work under sendmail I'm not sure since I don't believe there is a Max Connections type throttle under sendmail and even if you set the tcp queue backlog to some high number like 2048, spamc might still timeout.
If spamc does timeout or can't connect, it just lets the message through by default. So with procmail, you might get spam slipping through if your spamd server is too busy.
Regards,
Rick
