Amavis and Spamassassin in Sarge
Hello all
I'm writing to this list because I'm not completely sure about the cause of my
problem. The problem is that I have recently started to get the following
errors in my /var/log/mail.info:
Jan 17 20:22:25 dogbert amavis[988]: (00988-02) SA TIMED OUT, backtrace: at
/usr/share/perl5/Mail/SpamAssassin/BayesStore.pm line 376\n\teval {...} called
at /usr/share/perl5/Mail/SpamAssassin/BayesStore.pm line
376\n\tMail::SpamAssassin::BayesStore::upgrade_db('Mail::SpamAssassin::BayesStore=HASH(0x96cd4dc)')
called at /usr/share/perl5/Mail/SpamAssassin/BayesStore.pm line
253\n\tMail::SpamAssassin::BayesStore::tie_db_writable('Mail::SpamAssassin::BayesStore=HASH(0x96cd4dc)')
called at /usr/share/perl5/Mail/SpamAssassin/Bayes.pm line 662\n\teval {...}
called at /usr/share/perl5/Mail/SpamAssassin/Bayes.pm line
655\n\tMail::SpamAssassin::Bayes::learn('Mail::SpamAssassin::Bayes=HASH(0x970fa04)',
0, 'Mail::SpamAssassin::NoMailAudit=HASH(0x9b15bdc)', 'undef') called at
/usr/share/perl5/Mail/SpamAssassin/PerMsgLearner.pm line
110\n\tMail::SpamAssassin::PerMsgLearner::learn_ham('Mail::SpamAssassin::PerMsgLearner=HASH(0x9c4a64c)',
'undef') called at /...
That example is the first instance of such messages ever, but since that this
has been happening on regular basis. I have made no changes to any
configuration files. I think that spamassassin was upgraded near that date, but
I'm not sure. I now disabled spam scanning from amavis and this is not happening
anymore, but this result does not please me.
I would like to have some help with this matter - or maybe this is a bug? I'm
running Debian Sarge with 2.6.9-kernel. I use Postfix as my MTA and
amavisd-new+spamassassin+clamav for virus/spamscanning.
If there's any other info you need, I'll be happy to supply (when I figure out
how these mailing lists actually work:)
Thank you very much.
----------------------------------------------------------------
This mail sent through L-secure: http://www.l-secure.net/
Reply to: