RulesDuJour problem
Greetings folks; I just installed RulesDuJour, and ran it once by hand. It wasn't labeling the subject line, so I edited my local.cf to turn that on, didn't change anything else, but now a 'service spamd restart' fails with this error message nomograph: Starting spamd: [20715] warn: Value ax-conn-per-child=50 invalid for option m (number expected) [20715] warn: Unknown option: a [20715] warn: Unknown option: c And spits out the rest of its --help message. However, 'spamassassin --lint' returns clean in about 4 seconds. Humm, /etc/sysconfig/spamassassin had an .rpmnew appended, fixed that. Which is odd as removeing that startup SPAMDOPTION in the /etc/init.d/spamd file didn't get rid of the message. Odd indeed. Also, the startup says there should be 5 (-m5) copies of spamd running, but a ps -ea|grep spamd only finds 3. Another one of those things that make you go hu, I guess. Any comments on how to reduce the hu? -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.36% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: RulesDuJour problem
On Sun, Dec 04, 2005 at 10:41:07PM -0500, Gene Heskett wrote: Greetings folks; I just installed RulesDuJour, and ran it once by hand. It wasn't labeling the subject line, so I edited my local.cf to turn that on, didn't change anything else, but now a 'service spamd restart' fails with this error message nomograph: Starting spamd: [20715] warn: Value ax-conn-per-child=50 invalid for option m (number expected) [20715] warn: Unknown option: a [20715] warn: Unknown option: c And spits out the rest of its --help message. However, 'spamassassin --lint' returns clean in about 4 seconds. Humm, /etc/sysconfig/spamassassin had an .rpmnew appended, fixed that. Which is odd as removeing that startup SPAMDOPTION in the /etc/init.d/spamd file didn't get rid of the message. Odd indeed. Also, the startup says there should be 5 (-m5) copies of spamd running, but a ps -ea|grep spamd only finds 3. Another one of those things that make you go hu, I guess. Any comments on how to reduce the hu? -- Cheers, Gene The spamd options are located in two places - in /etc/sysconfig/spamassassin and in the main script, /etc/rc.d/init.d/spamd (or whatever you called it). Long option names are preceded by two dashes. Somewhere you have -max-conn-per-child=50 where you should have --max-conn-per-child=50 Look over man spamd and check your options against that. Cheers, -- Bob McClure, Jr. Bobcat Open Systems, Inc. [EMAIL PROTECTED] http://www.bobcatos.com Peace at any price is inflationary.
Re: RulesDuJour problem
From: Gene Heskett [EMAIL PROTECTED]
Greetings folks;
I just installed RulesDuJour, and ran it once by hand. It wasn't
labeling the subject line, so I edited my local.cf to turn that on,
didn't change anything else, but now a 'service spamd restart'
fails with this error message nomograph:
Starting spamd: [20715] warn: Value ax-conn-per-child=50 invalid for
option m (number expected)
[20715] warn: Unknown option: a
[20715] warn: Unknown option: c
And spits out the rest of its --help message.
However, 'spamassassin --lint' returns clean in about 4 seconds.
Humm, /etc/sysconfig/spamassassin had an .rpmnew appended, fixed that.
Which is odd as removeing that startup SPAMDOPTION in the
/etc/init.d/spamd file didn't get rid of the message. Odd indeed.
Also, the startup says there should be 5 (-m5) copies of spamd running,
but a ps -ea|grep spamd only finds 3. Another one of those things that
make
you go hu, I guess.
Any comments on how to reduce the hu?
I suffer from lack of informationitis here.
What is the line that starts the spamd service?
The above suggests you have a typo somewhere. Like maybe something
like -m ax-conn-per-child=50 instead of -max-conn-per-child=50.
{^_^}
Re: RulesDuJour problem
From: Bob McClure Jr [EMAIL PROTECTED]
On Sun, Dec 04, 2005 at 10:41:07PM -0500, Gene Heskett wrote:
Greetings folks;
I just installed RulesDuJour, and ran it once by hand. It wasn't
labeling the subject line, so I edited my local.cf to turn that on,
didn't change anything else, but now a 'service spamd restart'
fails with this error message nomograph:
Starting spamd: [20715] warn: Value ax-conn-per-child=50 invalid for
option m (number expected)
[20715] warn: Unknown option: a
[20715] warn: Unknown option: c
And spits out the rest of its --help message.
However, 'spamassassin --lint' returns clean in about 4 seconds.
Humm, /etc/sysconfig/spamassassin had an .rpmnew appended, fixed that.
Which is odd as removeing that startup SPAMDOPTION in the
/etc/init.d/spamd file didn't get rid of the message. Odd indeed.
Also, the startup says there should be 5 (-m5) copies of spamd running,
but a ps -ea|grep spamd only finds 3. Another one of those things that
make
you go hu, I guess.
Any comments on how to reduce the hu?
--
Cheers, Gene
The spamd options are located in two places - in
/etc/sysconfig/spamassassin and in the main script,
/etc/rc.d/init.d/spamd (or whatever you called it). Long option names
are preceded by two dashes. Somewhere you have
-max-conn-per-child=50
where you should have
--max-conn-per-child=50
I like your answer better than mind. Fogs of hunger caught me.
{^_-}
Re: RulesDuJour problem
On Sunday 04 December 2005 22:46, Bob McClure Jr wrote: --max-conn-per-child=50 ?? Thats also odd, 3.04 has been running just fine with that single dash option for at least 6 months. Wierd. Anyway I put it back in like above, and that works. Now to figure out why, with a -m5 setting, its only running 3 copies of spamd. Thanks Bob. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.36% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
RulesDuJour problem - help please
Happy New Year to all. Ive searched the list archive, and found some references to my problem, but no solutions, so here goes again (sorry for the long post, but I want to provide as much info. as necessary): I recently upgraded to spamassassin 3.0.2 running on CentOS 3.3. Im also running sendmail-8.12.11-4.RHEL3.1 and mailscanner-4.37.7-1. Ive been using RulesDuJour since before the latest versions of the above software, and it worked fine. However, after upgrading to spamassassin 3.0.2, RulesDuJour now fails. Heres some of the more salient output from running the script: ***WARNING***: spamassassin --lint failed. Rolling configuration files back, not restarting SpamAssassin. Rollback command is: mv -f /usr/share/spamassassin/tripwire.cf /usr/share/spamassassin/RulesDuJour/99_FVGT_Tripwire.cf.2; rm -f /usr/share/spamassassin/tripwire.cf; mv -f /usr/share/spamassassin/evilnumbers.cf /usr/share/spamassassin/RulesDuJour/evilnumbers.cf.2; rm -f /usr/share/spamassassin/evilnumbers.cf; mv -f /usr/share/spamassassin/70_sare_random.cf /usr/share/spamassassin/RulesDuJour/70_sare_random.cf.2; rm -f /usr/share/spamassassin/70_sare_random.cf; mv -f /usr/share/spamassassin/antidrug.cf /usr/share/spamassassin/RulesDuJour/antidrug.cf.2; rm -f /usr/share/spamassassin/antidrug.cf; mv -f /usr/share/spamassassin/bigevil.cf /usr/share/spamassassin/RulesDuJour/bigevil.cf.2; rm -f /usr/share/spamassassin/bigevil.cf; mv -f /usr/share/spamassassin/blacklist.cf /usr/share/spamassassin/RulesDuJour/sa-blacklist.current.2; rm -f /usr/share/spamassassin/blacklist.cf; mv -f /usr/share/spamassassin/bogus-virus-warnings.cf /usr/share/spamassassin/RulesDuJour/bogus-virus-warnings.cf.2; rm -f /usr/share/spamassassin/bogus-virus-warnings.cf; mv -f /usr/share/spamassassin/70_sare_ratware.cf /usr/share/spamassassin/RulesDuJour/70_sare_ratware.cf.2; rm -f /usr/share/spamassassin/70_sare_ratware.cf; mv -f /usr/share/spamassassin/70_sare_spoof.cf /usr/share/spamassassin/RulesDuJour/70_sare_spoof.cf.2; rm -f /usr/share/spamassassin/70_sare_spoof.cf; mv -f /usr/share/spamassassin/70_sare_bayes_poison_nxm.cf /usr/share/spamassassin/RulesDuJour/70_sare_bayes_poison_nxm.cf.2; rm -f /usr/share/spamassassin/70_sare_bayes_poison_nxm.cf; mv -f /usr/share/spamassassin/70_sare_specific.cf /usr/share/spamassassin/RulesDuJour/70_sare_specific.cf.2; rm -f /usr/share/spamassassin/70_sare_specific.cf; mv -f /usr/share/spamassassin/70_sare_adult.cf /usr/share/spamassassin/RulesDuJour/70_sare_adult.cf.2; rm -f /usr/share/spamassassin/70_sare_adult.cf; Lint output: config: SpamAssassin failed to parse line, skipping: !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN config: SpamAssassin failed to parse line, skipping: HTMLHEAD config: SpamAssassin failed to parse line, skipping: TITLE Rate limiting in effect/TITLE config: SpamAssassin failed to parse line, skipping: /HEADBODY config: SpamAssassin failed to parse line, skipping: H1Rate limiting in effect/H1 config: SpamAssassin failed to parse line, skipping: Your request could not be processed because you have exceeded the maximum request rate for the requested document. This is a temporary condition; you will be permitted to submit another request in a few hours. config: SpamAssassin failed to parse line, skipping: BRBRTo avoid triggering the rate limiter in future, please make less frequent requests for this document. You should not request the same document more than once every 24 hours. Please also note that continuing to re-request the document while rate limiting is in effect will further increase the amount of time before the file becomes available to you again. config: SpamAssassin failed to parse line, skipping: P config: SpamAssassin failed to parse line, skipping: HR config: SpamAssassin failed to parse line, skipping: /BODY/HTML config: SpamAssassin failed to parse line, skipping: !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN config: SpamAssassin failed to parse line, skipping: HTMLHEAD config: SpamAssassin failed to parse line, skipping: TITLE Rate limiting in effect/TITLE config: SpamAssassin failed to parse line, skipping: /HEADBODY config: SpamAssassin failed to parse line, skipping: H1Rate limiting in effect/H1 config: SpamAssassin failed to parse line, skipping: Your request could not be processed because you have exceeded the maximum request rate for the requested document. This is a temporary condition; you will be permitted to submit another request in a few hours. config: SpamAssassin failed to parse line, skipping: BRBRTo avoid triggering the rate limiter in future, please make less frequent requests for this document. You should not request the same document more than once every 24 hours. Please also note that continuing to re-request the document while rate limiting is in effect will further increase the amount of time before the file becomes available to you again. config: SpamAssassin failed to parse line, skipping: P config: SpamAssassin failed to
RE: RulesDuJour problem - help please
-Original Message- Well, umh, uh, no. local.cf lives in /etc/mail/spamassassin. Rules live in /usr/share/spamassassin/RulesDuJour/. And the Bayes part I just today tried to make work. Do I (or rather, I do) have a misconfigured system? If so, (with humble apologies for my stupidity) how do I fix? Dimitri From: Richard Ozer [mailto:[EMAIL PROTECTED] Sent: Monday, January 03, 2005 10:21 AM To: Dimitri Yioulos Subject: Re: RulesDuJour problem - help please I notice that all your sa paths are pointing to /root/.spamassassin Is this correct? Is it possible that you have a local.cf in an incorrect location? Notice that the Bayes DB isn't tying either. Similarly, it seems to be located in /root/.spamassassin. RO Dimitri Yioulos wrote: Happy New Year to all. I've searched the list archive, and found some references to my problem, but no solutions, so here goes again (sorry for the long post, but I want to provide as much info. as necessary): I recently upgraded to spamassassin 3.0.2 running on CentOS 3.3. I'm also running sendmail-8.12.11-4.RHEL3.1 and mailscanner-4.37.7-1. I've been using RulesDuJour since before the latest versions of the above software, and it worked fine. However, after upgrading to spamassassin 3.0.2, RulesDuJour now fails. Here's some of the more salient output from running the script: ***WARNING***: spamassassin --lint failed. Rolling configuration files back, not restarting SpamAssassin. Rollback command is: mv -f /usr/share/spamassassin/tripwire.cf /usr/share/spamassassin/RulesDuJour/99_FVGT_Tripwire.cf.2; rm -f /usr/share/spamassassin/tripwire.cf; mv -f /usr/share/spamassassin/evilnumbers.cf /usr/share/spamassassin/RulesDuJour/evilnumbers.cf.2; rm -f /usr/share/spamassassin/evilnumbers.cf; mv -f /usr/share/spamassassin/70_sare_random.cf /usr/share/spamassassin/RulesDuJour/70_sare_random.cf.2; rm -f /usr/share/spamassassin/70_sare_random.cf; mv -f /usr/share/spamassassin/antidrug.cf /usr/share/spamassassin/RulesDuJour/antidrug.cf.2; rm -f /usr/share/spamassassin/antidrug.cf; mv -f /usr/share/spamassassin/bigevil.cf /usr/share/spamassassin/RulesDuJour/bigevil.cf.2; rm -f /usr/share/spamassassin/bigevil.cf; mv -f /usr/share/spamassassin/blacklist.cf /usr/share/spamassassin/RulesDuJour/sa-blacklist.current.2; rm -f /usr/share/spamassassin/blacklist.cf; mv -f /usr/share/spamassassin/bogus-virus-warnings.cf /usr/share/spamassassin/RulesDuJour/bogus-virus-warnings.cf.2; rm -f /usr/share/spamassassin/bogus-virus-warnings.cf; mv -f /usr/share/spamassassin/70_sare_ratware.cf /usr/share/spamassassin/RulesDuJour/70_sare_ratware.cf.2; rm -f /usr/share/spamassassin/70_sare_ratware.cf; mv -f /usr/share/spamassassin/70_sare_spoof.cf /usr/share/spamassassin/RulesDuJour/70_sare_spoof.cf.2; rm -f /usr/share/spamassassin/70_sare_spoof.cf; mv -f /usr/share/spamassassin/70_sare_bayes_poison_nxm.cf /usr/share/spamassassin/RulesDuJour/70_sare_bayes_poison_nxm.cf.2; rm -f /usr/share/spamassassin/70_sare_bayes_poison_nxm.cf; mv -f /usr/share/spamassassin/70_sare_specific.cf /usr/share/spamassassin/RulesDuJour/70_sare_specific.cf.2; rm -f /usr/share/spamassassin/70_sare_specific.cf; mv -f /usr/share/spamassassin/70_sare_adult.cf /usr/share/spamassassin/RulesDuJour/70_sare_adult.cf.2; rm -f /usr/share/spamassassin/70_sare_adult.cf; Lint output: config: SpamAssassin failed to parse line, skipping: !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN config: SpamAssassin failed to parse line, skipping: HTMLHEAD config: SpamAssassin failed to parse line, skipping: TITLE Rate limiting in effect/TITLE config: SpamAssassin failed to parse line, skipping: /HEADBODY config: SpamAssassin failed to parse line, skipping: H1Rate limiting in effect/H1 config: SpamAssassin failed to parse line, skipping: Your request could not be processed because you have exceeded the maximum request rate for the requested document. This is a temporary condition; you will be permitted to submit another request in a few hours. config: SpamAssassin failed to parse line, skipping: BRBRTo avoid triggering the rate limiter in future, please make less frequent requests for this document. You should not request the same document more than once every 24 hours. Please also note that continuing to re-request the document while rate limiting is in effect will further increase the amount of time before the file becomes available to you again. config: SpamAssassin failed to parse line, skipping: P config: SpamAssassin failed to parse line, skipping: HR config: SpamAssassin failed to parse line, skipping: /BODY/HTML config: SpamAssassin failed to parse line, skipping: !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN config: SpamAssassin failed to parse line, skipping: HTMLHEAD config: SpamAssassin failed to parse line, skipping: TITLE Rate limiting
RE: RulesDuJour problem - help please
Loren, Cron is set to get the rules at 1:30 AM each day. Even those fetches fail. So, although I appreciate the tip, it's not the cause of my problem. Dimitri -Original Message- From: Loren Wilton [mailto:[EMAIL PROTECTED] Sent: Monday, January 03, 2005 10:28 AM To: Dimitri Yioulos Subject: Re: RulesDuJour problem - help please config: SpamAssassin failed to parse line, skipping: TITLE Rate limiting in effect/TITLE Notice the text between TITLE and /TITLE. You can only get the rules a maximum of I believe 3 times in a 24 hour period. Since they don't change very often, this is more than enough; in fact once a day should be more than enough. Check you cron script to make sure you aren't trying to get them once a second or so. Loren
Re: RulesDuJour problem - help please
Hi Dimitri, Dimitri Yioulos wrote: Happy New Year to all. Ive searched the list archive, and found some references to my problem, but no solutions, so here goes again (sorry for the long post, but I want to provide as much info. as necessary): I recently upgraded to spamassassin 3.0.2 running on CentOS 3.3. Im also running sendmail-8.12.11-4.RHEL3.1 and mailscanner-4.37.7-1. Ive been using RulesDuJour since before the latest versions of the above software, and it worked fine. However, after upgrading to spamassassin 3.0.2, RulesDuJour now fails. Heres some of the more salient output from running the script: ***WARNING***: spamassassin --lint failed. snip Lint output: config: SpamAssassin failed to parse line, skipping: !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN config: SpamAssassin failed to parse line, skipping: HTMLHEAD config: SpamAssassin failed to parse line, skipping: TITLE Rate limiting in effect/TITLE config: SpamAssassin failed to parse line, skipping: /HEADBODY config: SpamAssassin failed to parse line, skipping: H1Rate limiting in effect/H1 config: SpamAssassin failed to parse line, skipping: Your request could not be processed because you have exceeded the maximum request rate for the requested document. This is a temporary condition; you will be permitted to submit another request in a few hours. config: SpamAssassin failed to parse line, skipping: BRBRTo avoid triggering the rate limiter in future, please make less frequent requests for this document. You should not request the same document more than once every 24 hours. Please also note that continuing to re-request the document while rate limiting is in effect will further increase the amount of time before the file becomes available to you again. snip Check which files have the string Rage limiting in them. [EMAIL PROTECTED] grep -l Rate limiting /usr/share/spamassassin/* [EMAIL PROTECTED] grep -l Rate limiting /usr/share/spamassassin/RulesDuJour/* Delete those files. In fact you can delete everything in /usr/share/spamassassin/RulesDuJour/ and it should rebuild itself. Finally, you should not have RDJ pointing to /usr/share/spamassassin. The proper place for local configuration (local.cf) and local rulesets (rules_du_jour managed rulesets) is /etc/spamassassin or /etc/mail/spamassassin (or similar... based on OS conventions) Id really like to get RuulesDuJour working again. Can anybody help? Thanks. Dimitri Hope this helps. Chris Thielen signature.asc Description: OpenPGP digital signature
RE: RulesDuJour problem - help please
-Original Message- From: Chris Thielen [mailto:[EMAIL PROTECTED] Sent: Monday, January 03, 2005 11:44 AM To: Dimitri Yioulos Cc: users@spamassassin.apache.org Subject: Re: RulesDuJour problem - help please Hi Dimitri, Dimitri Yioulos wrote: Happy New Year to all. I've searched the list archive, and found some references to my problem, but no solutions, so here goes again (sorry for the long post, but I want to provide as much info. as necessary): I recently upgraded to spamassassin 3.0.2 running on CentOS 3.3. I'm also running sendmail-8.12.11-4.RHEL3.1 and mailscanner-4.37.7-1. I've been using RulesDuJour since before the latest versions of the above software, and it worked fine. However, after upgrading to spamassassin 3.0.2, RulesDuJour now fails. Here's some of the more salient output from running the script: ***WARNING***: spamassassin --lint failed. snip Lint output: config: SpamAssassin failed to parse line, skipping: !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN config: SpamAssassin failed to parse line, skipping: HTMLHEAD config: SpamAssassin failed to parse line, skipping: TITLE Rate limiting in effect/TITLE config: SpamAssassin failed to parse line, skipping: /HEADBODY config: SpamAssassin failed to parse line, skipping: H1Rate limiting in effect/H1 config: SpamAssassin failed to parse line, skipping: Your request could not be processed because you have exceeded the maximum request rate for the requested document. This is a temporary condition; you will be permitted to submit another request in a few hours. config: SpamAssassin failed to parse line, skipping: BRBRTo avoid triggering the rate limiter in future, please make less frequent requests for this document. You should not request the same document more than once every 24 hours. Please also note that continuing to re-request the document while rate limiting is in effect will further increase the amount of time before the file becomes available to you again. snip Check which files have the string Rage limiting in them. [EMAIL PROTECTED] grep -l Rate limiting /usr/share/spamassassin/* [EMAIL PROTECTED] grep -l Rate limiting /usr/share/spamassassin/RulesDuJour/* Delete those files. In fact you can delete everything in /usr/share/spamassassin/RulesDuJour/ and it should rebuild itself. Finally, you should not have RDJ pointing to /usr/share/spamassassin. The proper place for local configuration (local.cf) and local rulesets (rules_du_jour managed rulesets) is /etc/spamassassin or /etc/mail/spamassassin (or similar... based on OS conventions) I'd really like to get RuulesDuJour working again. Can anybody help? Thanks. Dimitri Hope this helps. Chris Thielen Chris, Many thanks. I did as you suggested, and all now seems to work. Dimitri
