On Sun, 21 Mar 2004 13:43:24 -0300, Gustavo Michels <[EMAIL PROTECTED]> wrote: > >I was first asking about SA's performance and I had a tip from the list to use >spamd/spamc instead of the regular spamassassin client. I did that but the >problem still continues. SpamAssassin will take 5 minutes to classify the >first message. > >So I turned on debugging and I am attaching the debug log so maybe someone can >help me out. I also thought of filing a bug, but I'd better ask to the list >first. > >Here's the log with the message that makes SA wait for 5 minutes with 100% cpu >usage: > >spamd[5975]: [debug] bayes: Can't use estimation method for expiry, something >fishy, calculating optimal atime delta (first pass)_
SA is *not* waiting or hanging for five minutes. It's busy analyzing your bayes database to find an appropriate expiry time. Your bayes database is about six times "bayes_journal_max_size" and doesn't look like it has been used much in the last 64 days. As a result, SA can't find an appropriate expire time and attempts to automatically expire the database again at a later time. I suggest you turn off auto expiry by adding "bayes_auto_expire 0" to your user_prefs file and attempt a manual expiry every few days with "sa-learn --force-expire". Hope this helps, Alan -- Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html
