Originally Posted by till
2) The problem is that ISPCOnfig calls spamassassin instead of the spamc / spamd combination. We can not simply switch beacuse spamd is not able to read the current spamassassin config files. A solution might be to symlink from the file location spamd expects to the current spamassassin config file for every useraccount. We will start working on a solution for that in the ISPConfig dev branch shortly.
Thanks Till, in the mean time we have disabled spamassasin for the 3 thousand users of our bigger domain and we are configuring graylisting and adding RBL in postfix, trying to reduce the amount of mail received from each account.
At now we have some time during each day where the load average jump over 100 for the concurrent presence of many clamscan processes.
There is also another task that is always present during the day, but I suppose it should terminate during the night
15111 root 39 17 3084 904 624 R 99.9 0.0 5:20.82 grep -iw postfix /var/log/mail.log.07-09-06_23-59-01
I will study some code...