Eric Yellin schrieb:
OK I seem to have found the culprit. It seems to be the size of the signature directory... Felix, I think you suspected this earlier...
I'm not sure if the size is the root cause. As root does not experience your problems, it may be caused by some specified data items in zimbra's profile.
I renamed the 'zimbra' signature directory and let DSPAM recreate a new one. Once I did that spam checking was instantaneous.
I expected that as root did not have the problem. Basically, you just created a new user profile and lost your dspam database. This may be a good enough workaround if you need dspam working NOW but you don't why it happened and if it will happen again. Please do not delete your signature directory but investigate the issue a bit further.
What does DSPAM do? with the signature files?
The signature data contains all tokens extracted from the processed mail. With this information dspam is able to retrain specific tokens given a dspam message id. I don't know if this data is read when you only process a mail... Unfortunately, you did not answer this question
Btw: While you pipe a mail through dspam, does the dspam process use up all your free cpu time or does it just wait? Maybe it waits for a connection to clamd/mysql...
You can check that? An strace of the dspam call would be nice, too. fs
