You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Kevin Thorpe <ke...@pricetrak.com> on 2004/10/29 12:32:39 UTC
SpamAssassin timing out in Message.pm
I've suddenly started getting problems with SpamAssassin timing out. I
upgraded to Mail::SpamAssassin 3.0.1 first with no luck.
Initially the timeouts were in the bayes store so I turned
bayes_auto_expire off and now the timeout has moved to Message.pm.
Oct 29 10:59:14 linux amavis[28527]: (28527-01) SA TIMED OUT, backtrace:
at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/M
essage.pm line 116\n\teval {...} called at
/usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Message.pm line
116\n\tMail::SpamA
ssassin::Message::new('Mail::SpamAssassin::NoMailAudit') called at
/usr/lib/perl5/vendor_perl/5.8.0/Mail/SpamAssassin/NoMailAu
dit.pm line
34\n\tMail::SpamAssassin::NoMailAudit::new('Mail::SpamAssassin::NoMailAudit','data','ARRAY(0x926c1a4)','add_From_l
ine',0) called at (eval 38) line 161\n\teval {...} called at (eval 38)
line 149\n\tAmavis::SpamControl::spam_scan('Amavis::In:
:Connection=HASH(0x967eb90)','Amavis::In::Message=HASH(0x9a07040)')
called at /usr/sbin/amavisd line 5342\n\teval {...} called
at /usr/sbin/amavisd line
5138\n\tAmavis::check_mail('Amavis::In::Connection=HASH(0x967eb90)','Amavis::In::Message=HASH(0x9a0
7040)',0,'/tmp/amavis-20041029T105852-28527') called at (eval 36) line
356\n\tA...
I'm running Mail::SpamAssassin under amavisd-new . I tried adjusting the
child timeout in Amavis but It's not that. The timeout is at only
10-15 seconds.
Can anyone suggest why this is happening?
Thanks
--
Kevin Thorpe
Head of IT
Purchasing Index Ltd
Tel: (+44) 20 7350 4200
Mailto: kevin@pricetrak.com <ma...@pricetrak.com>
URL: http://www.pricetrak.com
------------------------------------------------------------------------
All views or opinions expressed in this message are solely those of the
author. Accordingly, Purchasing Index Ltd does not accept responsibility
for the contents of the message unless specifically stated otherwise. If
you have received this message in error, please notify the sender and
delete the message immediately.
Re: SpamAssassin timing out in Message.pm
Posted by Keith Hackworth <ke...@rpemail.com>.
> I've suddenly started getting problems with SpamAssassin timing out. I
> upgraded to Mail::SpamAssassin 3.0.1 first with no luck.
> Initially the timeouts were in the bayes store so I turned
> bayes_auto_expire off and now the timeout has moved to Message.pm.
>
> Oct 29 10:59:14 linux amavis[28527]: (28527-01) SA TIMED OUT, backtrace:
> at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/M
> essage.pm line 116\n\teval {...} called at
> /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Message.pm line
> 116\n\tMail::SpamA
> ssassin::Message::new('Mail::SpamAssassin::NoMailAudit') called at
> /usr/lib/perl5/vendor_perl/5.8.0/Mail/SpamAssassin/NoMailAu
> dit.pm line
> 34\n\tMail::SpamAssassin::NoMailAudit::new('Mail::SpamAssassin::NoMailAudit','data','ARRAY(0x926c1a4)','add_From_l
> ine',0) called at (eval 38) line 161\n\teval {...} called at (eval 38)
> line 149\n\tAmavis::SpamControl::spam_scan('Amavis::In:
> :Connection=HASH(0x967eb90)','Amavis::In::Message=HASH(0x9a07040)')
> called at /usr/sbin/amavisd line 5342\n\teval {...} called
> at /usr/sbin/amavisd line
> 5138\n\tAmavis::check_mail('Amavis::In::Connection=HASH(0x967eb90)','Amavis::In::Message=HASH(0x9a0
> 7040)',0,'/tmp/amavis-20041029T105852-28527') called at (eval 36) line
> 356\n\tA...
>
> I'm running Mail::SpamAssassin under amavisd-new . I tried adjusting the
> child timeout in Amavis but It's not that. The timeout is at only
> 10-15 seconds.
>
> Can anyone suggest why this is happening?
>
> Thanks
> --
> Kevin Thorpe
> Head of IT
> Purchasing Index Ltd
> Tel: (+44) 20 7350 4200
> Mailto: kevin@pricetrak.com <ma...@pricetrak.com>
> URL: http://www.pricetrak.com
> ------------------------------------------------------------------------
> All views or opinions expressed in this message are solely those of the
> author. Accordingly, Purchasing Index Ltd does not accept responsibility
> for the contents of the message unless specifically stated otherwise. If
> you have received this message in error, please notify the sender and
> delete the message immediately.
>
We had a similar problem with Amavis hanging on us. Are you running
Amavis or Amavis-new? Amavis-new came out with a new version last month
(2.1.2) - we installed it and it seemed to have fixed our problem.
Keith
Re: SpamAssassin timing out in Message.pm
Posted by Theo Van Dinter <fe...@kluge.net>.
On Fri, Oct 29, 2004 at 11:32:39AM +0100, Kevin Thorpe wrote:
> Oct 29 10:59:14 linux amavis[28527]: (28527-01) SA TIMED OUT, backtrace:
> at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/M
> essage.pm line 116\n\teval {...} called at
> /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Message.pm line
> 116\n\tMail::SpamA
> ssassin::Message::new('Mail::SpamAssassin::NoMailAudit') called at
> /usr/lib/perl5/vendor_perl/5.8.0/Mail/SpamAssassin/NoMailAu
> dit.pm line
Well, the problem is you're using NoMailAudit which was replaced by
Message. NMA no longer exists in 3.x. aka: your calling daemon and/or
your install is borked.
--
Randomly Generated Tagline:
"Good judgment comes from bad experience, and a lot of that comes from
bad judgment." - Zen Musings
Re: SpamAssassin timing out in Message.pm
Posted by Martin Hepworth <ma...@solid-state-logic.com>.
Kevin
I use MailScanner rather than Amavi-new, but...
have you tried sa-learn --force-expire to clear out the bayes info..
any RBL's in there??? have you tried removing them (setting score to zero).
what does spamassassin --lint give yo?
--
Martin Hepworth
Snr Systems Administrator
Solid State Logic
Tel: +44 (0)1865 842300
Kevin Thorpe wrote:
> I've suddenly started getting problems with SpamAssassin timing out. I
> upgraded to Mail::SpamAssassin 3.0.1 first with no luck.
> Initially the timeouts were in the bayes store so I turned
> bayes_auto_expire off and now the timeout has moved to Message.pm.
>
> Oct 29 10:59:14 linux amavis[28527]: (28527-01) SA TIMED OUT, backtrace:
> at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/M
> essage.pm line 116\n\teval {...} called at
> /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Message.pm line
> 116\n\tMail::SpamA
> ssassin::Message::new('Mail::SpamAssassin::NoMailAudit') called at
> /usr/lib/perl5/vendor_perl/5.8.0/Mail/SpamAssassin/NoMailAu
> dit.pm line
> 34\n\tMail::SpamAssassin::NoMailAudit::new('Mail::SpamAssassin::NoMailAudit','data','ARRAY(0x926c1a4)','add_From_l
> ine',0) called at (eval 38) line 161\n\teval {...} called at (eval 38)
> line 149\n\tAmavis::SpamControl::spam_scan('Amavis::In:
> :Connection=HASH(0x967eb90)','Amavis::In::Message=HASH(0x9a07040)')
> called at /usr/sbin/amavisd line 5342\n\teval {...} called
> at /usr/sbin/amavisd line
> 5138\n\tAmavis::check_mail('Amavis::In::Connection=HASH(0x967eb90)','Amavis::In::Message=HASH(0x9a0
> 7040)',0,'/tmp/amavis-20041029T105852-28527') called at (eval 36) line
> 356\n\tA...
>
> I'm running Mail::SpamAssassin under amavisd-new . I tried adjusting the
> child timeout in Amavis but It's not that. The timeout is at only
> 10-15 seconds.
>
> Can anyone suggest why this is happening?
>
> Thanks
> --
> Kevin Thorpe
> Head of IT
> Purchasing Index Ltd
> Tel: (+44) 20 7350 4200
> Mailto: kevin@pricetrak.com <ma...@pricetrak.com>
> URL: http://www.pricetrak.com
> ------------------------------------------------------------------------
> All views or opinions expressed in this message are solely those of the
> author. Accordingly, Purchasing Index Ltd does not accept responsibility
> for the contents of the message unless specifically stated otherwise. If
> you have received this message in error, please notify the sender and
> delete the message immediately.
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote confirms that this email message has been swept
for the presence of computer viruses and is believed to be clean.
**********************************************************************