Re: SPAMD taking over 300 secs

[Johnny B.]

i ran into something similar with spamassassin and its use of the bayes db for individual users over nfs.  if your mail message store for the users is available over nfs you might have a bayes database locking/lock file issue which in my case wound up extending delivery times to close to 300 seconds.  i also had network collisions which loaded the server unnecessarily so check that your network interface isn't experiencing issues as well otherwise load will be high and performance will really suffer.   use the command ifconig and look at the stats it'll show if there are errors.    if your users' mail message store isn't over nfs then you may also need a machine which has more processing power available, not sure what type of hardware you are trying to run this on with what additional software you are running and what youre trying to support more info is needed to determine root cause. cheers jb Asif Iqbal wrote: JGrotepass wrote: Asif Iqbal wrote: Is there a way I can limit the amount of memory the spamd can use and and the total size of mesg it scans? As I see that you're using qmail. I just found that the parm "-s xxxx" for the "spamc" does limit the size of the mail that is scanned. The default value (no -s Parm) is 250K. How are you feeding the mail from Qmail to Spamd? qmail-scanner-queue.pl calls spamc like that /usr/local/bin/spamc -c -f Regards, Jochen