Re: spamd keeps running at 99% CPU until i kill the process

Stuart Gall wrote: On 30 Aug 2007, at 16:55, Micke Andersson wrote: Richard Hobbs wrote: 421 SMTP incoming data timeout - message abandoned Hi, I have had exactly the same problem as you, with about the very same setup as you! The problem where actually a TCP problem, and not a Spam

Re: spamd keeps running at 99% CPU until i kill the process

On 11 Sep 2007, at 05:15, Thomas Schulz wrote: On 30 Aug 2007, at 16:55, Micke Andersson wrote: Richard Hobbs wrote: Hello, To add information to this problem, it appears that spamd does eventually give up after 5 minutes - which then bounces the message back to the sender stating: 421 S

Re: spamd keeps running at 99% CPU until i kill the process

> On 30 Aug 2007, at 16:55, Micke Andersson wrote: > > > Richard Hobbs wrote: > >> Hello, > >> > >> To add information to this problem, it appears that spamd does > >> eventually give up after 5 minutes - which then bounces the > >> message back > >> to the sender stating: > >> > >> 421 SMTP i

Re: spamd keeps running at 99% CPU until i kill the process

On 30 Aug 2007, at 16:55, Micke Andersson wrote: Richard Hobbs wrote: Hello, To add information to this problem, it appears that spamd does eventually give up after 5 minutes - which then bounces the message back to the sender stating: 421 SMTP incoming data timeout - message abandoned

Re: spamd keeps running at 99% CPU until i kill the process

JM> the stable tree is reliant on committers hand-copying the rules -- JM> and this hasn't been happening much recently. Idea: hand copy them anyway once a month or less in the interim.

Re: spamd keeps running at 99% CPU until i kill the process

Richard Hobbs wrote: Hello, Michael Parker wrote: Richard Hobbs wrote: Hello, Could the size of "bayes_seen" and "bayes_toks" be causing this timeout? No, those aren't really that big, but it does look like you have an expiration problem. I've heard that this file should be around 10MB on

Re: spamd keeps running at 99% CPU until i kill the process

Rules for the SVN version are promoted and demoted automatically, and updates are generated without human intervention. However, it's potentially unstable, and could cause false positives. We haven't yet had the time to work out an agreed way to implement a safe version of automatic update gener

Re: spamd keeps running at 99% CPU until i kill the process

Hello, Why is that? Surely updates are released for current, stable versions of spamassassin? Most of the world can't run SVN version! lol Any ideas why this might be? Thanks again, Richard. [EMAIL PROTECTED] wrote: >>> However, if there are no updates > > Which I bet you will be surprised to

Re: spamd keeps running at 99% CPU until i kill the process

>> However, if there are no updates Which I bet you will be surprised to find will always be the case these days, unless you use yet unreleased SVN versions of spamassassin.

Re: spamd keeps running at 99% CPU until i kill the process

Richard Hobbs wrote: Hello, To add information to this problem, it appears that spamd does eventually give up after 5 minutes - which then bounces the message back to the sender stating: 421 SMTP incoming data timeout - message abandoned Obviously, this cannot keep happening, but i don't kno

Re: spamd keeps running at 99% CPU until i kill the process

On Thu, 30 Aug 2007, Richard Hobbs wrote: > == > echo "Updating rules..." && /usr/bin/sa-update && echo "Done, now > checking config syntax..." && spamassassin --lint && echo "Done, now > restarting spamd..." && /etc/init.d/spamas

Re: spamd keeps running at 99% CPU until i kill the process

Hello, Sorry for so many emails, but it's sorted - removing "rewrite_subject 1" from the config does not stop the subject line from being rewritten, so i'm done! However, with regards to the cronjob, i'd like some intelligent reporting if possible, so i've constructed this: =

Re: spamd keeps running at 99% CPU until i kill the process

Hello, Don't worry - i know what lint does now, but when i run it, i get this: mail:/etc/cron.weekly# spamassassin --lint [25465] warn: config: failed to parse line, skipping: rewrite_subject 1 [25465] warn: lint: 1 issues detected, please rerun with debug enabled for more information mail:/etc/c

Re: spamd keeps running at 99% CPU until i kill the process

Hello, What does "spamassassin --lint" do? I can't find the lint option in the man page... Thanks again, Richard. John D. Hardin wrote: > On Wed, 29 Aug 2007, Richard Hobbs wrote: > >> Would you guys also recommend putting the command "/usr/bin/sa-update" >> in the crontab as well? >> >> If so

Re: spamd keeps running at 99% CPU until i kill the process

On Wed, 29 Aug 2007, Richard Hobbs wrote: > Would you guys also recommend putting the command "/usr/bin/sa-update" > in the crontab as well? > > If so, should i be using any particular parameters? And how often should > it be run to be worthwhile? I run it weekly... /etc/cron.weekly/spamassassi

Re: spamd keeps running at 99% CPU until i kill the process

Hello, Would you guys also recommend putting the command "/usr/bin/sa-update" in the crontab as well? If so, should i be using any particular parameters? And how often should it be run to be worthwhile? Thanks again, Richard. Richard Hobbs wrote: > Hello, > > Thank you - this is now done! :-)

Re: spamd keeps running at 99% CPU until i kill the process

Hello, Thank you - this is now done! :-) I shall see how it goes... Richard. Anthony Peacock wrote: > Hi, > > Richard Hobbs wrote: >> Hello, > > Is this all correct? >>> Yes. Set up expiration in a cron job, once per day is usually fine. >> >> OK, will do - i assume "sa-learn --f

Re: spamd keeps running at 99% CPU until i kill the process

Hi, Richard Hobbs wrote: Hello, Is this all correct? Yes. Set up expiration in a cron job, once per day is usually fine. OK, will do - i assume "sa-learn --force-expire" is the command to run via cron, right? Yup! This is my crontab line: 00 22 * * * /usr/local/bin/sa-learn --force-e

Re: spamd keeps running at 99% CPU until i kill the process

Hello, Anthony Peacock wrote: > Hi, > > Richard Hobbs wrote: >> Hello, >> >> John D. Hardin wrote: >>> On Tue, 28 Aug 2007, Richard Hobbs wrote: >>> Could the size of "bayes_seen" and "bayes_toks" be causing this timeout? >>> Yes. >>> If so, what can i do about this? >>> Disable au

Re: spamd keeps running at 99% CPU until i kill the process

On Tue, 28 Aug 2007, Richard Hobbs wrote: > Is this all correct? Spot on. > Would a suitable alternative be to delete "bayes_seen" and > "bayes_toks", then restart spamd? I know i would be deleting > everything that had been learned over the last period of time, but > starting afresh may not be

Re: spamd keeps running at 99% CPU until i kill the process

Hi, Richard Hobbs wrote: Hello, John D. Hardin wrote: On Tue, 28 Aug 2007, Richard Hobbs wrote: Could the size of "bayes_seen" and "bayes_toks" be causing this timeout? Yes. If so, what can i do about this? Disable automatic Bayes expiry and do a manual expiration run, and allow it to co

Re: spamd keeps running at 99% CPU until i kill the process

Hello, John D. Hardin wrote: > On Tue, 28 Aug 2007, Richard Hobbs wrote: > >> Could the size of "bayes_seen" and "bayes_toks" be causing this timeout? > > Yes. > >> If so, what can i do about this? > > Disable automatic Bayes expiry and do a manual expiration run, and > allow it to complete.

Re: spamd keeps running at 99% CPU until i kill the process

On Tue, 28 Aug 2007, Richard Hobbs wrote: > Could the size of "bayes_seen" and "bayes_toks" be causing this timeout? Yes. > If so, what can i do about this? Disable automatic Bayes expiry and do a manual expiration run, and allow it to complete. Once that's done you *can* turn automatic expir

Re: spamd keeps running at 99% CPU until i kill the process

Hello, One thing - you were given an excellent advice today on exim list by Graeme. Why don't you follow it? Anyway, this is probably your problem: http://spamassassin.apache.org/advisories/cve-2007-0451.txt Upgrade to 3.1.8 if you can. On Tue, 28 Aug 2007 15:09:14 +, Richard Hobbs <[EMAI

Re: spamd keeps running at 99% CPU until i kill the process

Hello, Michael Parker wrote: > Richard Hobbs wrote: >> Hello, >> >> Could the size of "bayes_seen" and "bayes_toks" be causing this timeout? >> > > No, those aren't really that big, but it does look like you have an > expiration problem. I've heard that this file should be around 10MB on a "stan

Re: spamd keeps running at 99% CPU until i kill the process

Richard Hobbs wrote: > Hello, > > Could the size of "bayes_seen" and "bayes_toks" be causing this timeout? > No, those aren't really that big, but it does look like you have an expiration problem. To solve your immediate problem you could just turn off bayes, that will get mail flowing again an

Re: spamd keeps running at 99% CPU until i kill the process

Hello, Could the size of "bayes_seen" and "bayes_toks" be causing this timeout? == mail:/home/spamcheck/.spamassassin# ls -l total 101060 -rw--- 1 spamcheck spamcheck 2637824 2007-08-28 12:42 auto-whitelist -rw--- 1 sp

Re: spamd keeps running at 99% CPU until i kill the process

Hello, Mark Martinec wrote: > Richard, > >> To add information to this problem, it appears that spamd does >> eventually give up after 5 minutes > > Capture a message causing touble from a MTA queue, > and feed it to a command line spamassassin with -t -D options. I would love to do this, but i

Re: spamd keeps running at 99% CPU until i kill the process

Richard, > To add information to this problem, it appears that spamd does > eventually give up after 5 minutes Capture a message causing touble from a MTA queue, and feed it to a command line spamassassin with -t -D options. Mark

Re: spamd keeps running at 99% CPU until i kill the process

Hello, To add information to this problem, it appears that spamd does eventually give up after 5 minutes - which then bounces the message back to the sender stating: 421 SMTP incoming data timeout - message abandoned Obviously, this cannot keep happening, but i don't know how to stop it... An

spamd keeps running at 99% CPU until i kill the process

Hello, We are running SpamAssassin version 3.1.7-deb running on Perl version 5.8.4 on a Debian Sarge box with exim4. I am using the following router: == sa_router: no_verify check_local_user # When to scan a message :