Mqueue.in huge

[Marcello Anderlini]

Thanks for your answer.
I've checked in in /root/.spamassassin and I found just this files.

-rw-------  1 root root 168087552 Jan 23 10:24 auto-whitelist
-rw-------  1 root root     97320 Jan 23 10:24 bayes_journal
-rw-------  1 root root 172904448 Jan 23 10:24 bayes_seen
-rw-------  1 root root 322408448 Jan 23 10:24 bayes_toks


This it's an extract of my Mailscanner.conf
==========================================================
Spam Score = yes
Cache SpamAssassin Results = yes
SpamAssassin Cache Database File =
/var/spool/MailScanner/incoming/SpamAssassin.cache.db
Rebuild Bayes Every = 0
Wait During Bayes Rebuild = no
==========================================================
It's correct ? Should I change something ? Maybe try to use an other
spamlist ?

Thanks again


Dr. Marcello Anderlini
m.anderlini at database.it
---------------------------------------------
Database Informatica S.r.l.
Microsoft Certified Partner
Tel.  +39059775070
Fax. +39059779545
http://www.database.it
---------------------------------------------

> -----Original Message-----
> From: mailscanner-bounces at lists.mailscanner.info
> [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf
> Of Glenn Steen
> Sent: lunedì 22 gennaio 2007 19.41
> To: MailScanner discussion
> Subject: Re: Mqueue.in huge
>
> On 22/01/07, Marcello Anderlini <m.anderlini at database.it> wrote:
> > Hello to all, I've tried to have a look to wiky but I did not found
> > any good answer for me.
> >
> > I'm using mailscanner 4.50.15 with spamassassin 3.1.7.1.el4.rf
> >
> > Some time the messagges in mqueue.in rise without any good reason
> > until 2000, I check dns and it seems work well, some time I
> get this
> > error:SpamAssassin timed out and was killed, failure 0 of 10. this
> > could be related with my problem ? I'm using CBL spam list.
> >
> > Thanks for any help and sorry for my worst english.
> >
> Hello Marcello,
>
> The SA timeouts are likely part and parcel off your problem.
> There are some likely spots where it is "failing":
> - bayes expiry taking "too long".
> - some more or less dead BL lookup (or other network test) timing out.
> - some "big" or "wrong" ruleset(s) making it take forever.
> ...
>
> Most likely is the first one (assuming you use bayes, of
> course:-). If you have some files like
> "bayes_toks.expire123456" in the same directory youstore your
> bayes database in, this is your problem (a well-known problem
> that has been penetrated more than once on this list).
> Instead of me repeating Scotts words, go read
> http://article.gmane.org/gmane.mail.virus.mailscanner/48068/ma
> tch=bayes+expire
> or search the archives for Matt Kettlers (final?!) words on
> SpamAssassin timeouts/bayes expiry:
> http://search.gmane.org/?query=bayes+expire&author=Matt+Kettle
r&group=gmane.mail.virus.mailscanner&sort=relevance&DEFAULTOP=and&xP=bayes%0
9expire&xFILTERS=Gmail.virus.mailscanner---A
>
> Matts writings also cover most (if not all) other measures
> one should do when SA is "timing out", so do browse the archives...:)
>
> BTW, Your english isn that bad... Try using the best next,
> and it'll be fine:-D Cheers
> --
> -- Glenn (who has to catch a train....->me running:-)
> email: glenn < dot > steen < at > gmail < dot > com
> work: glenn < dot > steen < at > ap1 < dot > se
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
> Before posting, read http://wiki.mailscanner.info/posting
>
> Support MailScanner development - buy the book off the website!
>
> --
> Messaggio verificato dal servizio antivirus di Database Informatica
>



-- 
Messaggio verificato dal servizio antivirus di Database Informatica