You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Ed Kasky <ed...@esson.net> on 2005/11/01 01:57:10 UTC
Problem with 70_sare_header.cf 01.03.16
When running rdj, I get the following:
Ruleset for header abuse (sets 0-3) has changed on yoda2.
Version line: # Version: 01.03.16
***WARNING***: spamassassin --lint failed.
Lint output: [25934] warn: config: warning: description exists for
non-existent rule SARE_HEAD_DATE_LONG1
[25934] warn: config: warning: score set for non-existent rule
SARE_HEAD_DATE_LONG1
I checked the file and found that there was a slight typo (I think):
header __SARE_HEAD_DATE_L1a Date =~ /.{50}/
header __SARE_HEAD_DATE_L1b Date =~ /added by/
meta SARE_HEAD_DATE_LONG1a __SARE_HEAD_DATE_L1a &&
!__SARE_HEAD_DATE_L1b
describe SARE_HEAD_DATE_LONG1 Date header has interesting length
score SARE_HEAD_DATE_LONG1 -0.500
tflags SARE_HEAD_DATE_LONG1 nice
I changed the meta line to:
meta SARE_HEAD_DATE_LONG1 __SARE_HEAD_DATE_L1a && !__SARE_HEAD_DATE_L1b
and it seems to have fixed it. I sent an email to the current maintainer,
Bob Menschel but thought I had better post it here as well just in case.
Ed Kasky
~~~~~~~~~
Randomly Generated Quote (169 of 489):
"Sometimes one pays most for the things one gets for nothing."
-- Albert Einstein
Re: Problem with 70_sare_header.cf 01.03.16
Posted by Chris Thielen <cm...@someone.dhs.org>.
Doc Schneider wrote:
>
> You need to re-download this rule set. I believe this was fixed **last
> yesterday*. *
>
hehe, that made me laugh out loud, thanks doc :)
Re: Problem with 70_sare_header.cf 01.03.16
Posted by Ed Kasky <ed...@esson.net>.
At 06:14 PM Monday, 10/31/2005, Doc Schneider wrote -=>
>Ed Kasky wrote:
>>When running rdj, I get the following:
>>Ruleset for header abuse (sets 0-3) has changed on yoda2.
>>Version line: # Version: 01.03.16
>>***WARNING***: spamassassin --lint failed.
>>Lint output: [25934] warn: config: warning: description exists for
>>non-existent rule SARE_HEAD_DATE_LONG1
>>[25934] warn: config: warning: score set for non-existent rule
>>SARE_HEAD_DATE_LONG1
>>I checked the file and found that there was a slight typo (I think):
>>header __SARE_HEAD_DATE_L1a Date =~ /.{50}/
>>header __SARE_HEAD_DATE_L1b Date =~ /added by/
>>meta SARE_HEAD_DATE_LONG1a __SARE_HEAD_DATE_L1a &&
>>!__SARE_HEAD_DATE_L1b
>>describe SARE_HEAD_DATE_LONG1 Date header has interesting length
>>score SARE_HEAD_DATE_LONG1 -0.500
>>tflags SARE_HEAD_DATE_LONG1 nice
>>I changed the meta line to:
>>meta SARE_HEAD_DATE_LONG1 __SARE_HEAD_DATE_L1a &&
>>!__SARE_HEAD_DATE_L1b
>>and it seems to have fixed it. I sent an email to the current
>>maintainer, Bob Menschel but thought I had better post it here as well
>>just in case.
>>Ed Kasky
>
>Ed,
>
>You need to re-download this rule set. I believe this was fixed last
>yesterday.
Doc,
Done - thanks....
Ed
~~~~~~~~~
Randomly Generated Quote (145 of 489):
"No man is above the law and no man is below it; nor do we ask any
man's permission when we require him to obey it. Obedience to the
law is demanded as a right; not asked as a favor."
--Theodore Roosevelt
Re: Problem with 70_sare_header.cf 01.03.16
Posted by Doc Schneider <ma...@maddoc.net>.
Ed Kasky wrote:
> When running rdj, I get the following:
>
> Ruleset for header abuse (sets 0-3) has changed on yoda2.
> Version line: # Version: 01.03.16
>
> ***WARNING***: spamassassin --lint failed.
>
> Lint output: [25934] warn: config: warning: description exists for
> non-existent rule SARE_HEAD_DATE_LONG1
> [25934] warn: config: warning: score set for non-existent rule
> SARE_HEAD_DATE_LONG1
>
> I checked the file and found that there was a slight typo (I think):
> header __SARE_HEAD_DATE_L1a Date =~ /.{50}/
> header __SARE_HEAD_DATE_L1b Date =~ /added by/
> meta SARE_HEAD_DATE_LONG1a __SARE_HEAD_DATE_L1a &&
> !__SARE_HEAD_DATE_L1b
> describe SARE_HEAD_DATE_LONG1 Date header has interesting length
> score SARE_HEAD_DATE_LONG1 -0.500
> tflags SARE_HEAD_DATE_LONG1 nice
>
> I changed the meta line to:
>
> meta SARE_HEAD_DATE_LONG1 __SARE_HEAD_DATE_L1a &&
> !__SARE_HEAD_DATE_L1b
>
> and it seems to have fixed it. I sent an email to the current
> maintainer, Bob Menschel but thought I had better post it here as well
> just in case.
>
> Ed Kasky
Ed,
You need to re-download this rule set. I believe this was fixed last
yesterday.
-Doc (SARE -- Ninja)