Hi, I am using spamassassin 3.0.2 with spamd. spamd is running all the time and the spamc processes are called from my MTA (exim) each time a message comes in and the receipient wants the message to be scanned.
spamd is called with the following options: --create-prefs --max-children 5 --helper-home-dir --syslog=/var/log/spamd.log -q --debug -d --pidfile=/var/run/spamd.pid It seems that the --max-children option doesn't do as one expects, since spamd now uses a preforking. And it seems that the processes are not limited at all. I forwarded around 70 messages to an email address that wants to have its mails scanned and I had problems with this. Since I am using SQL for userprefs, awl and bayes each process accesses the database (postgresql). This DB is limited to 32 concurrent connections. And those weren't enough for spamassassin. A lot of those mails couldn't be delivered because of this. Now my question is, what to do to limit concurrent spamd processes? And is it correct behaviour that the spamd processes give up, when the DB isn't accessible at some time? If they had tried it again, all mails could have been delivered. Regards Marco
