You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Casey King <ck...@lovebox.com> on 2005/12/01 17:42:24 UTC
Blacklist-uri.cf problem
As of this morning (aproximately 6:30am up to now.) all three of my
systems have failed to update RDJ. This is what I am getting as an
error.
Rules Du Jour Run Summary:RulesDuJour Run Summary on wks-lin9:
William Stearn's URI blacklist has changed on wks-lin9.
Version line: #sa-blacklist.uri: 200512010914
***WARNING***: spamassassin --lint failed.
Rolling configuration files back, not restarting SpamAssassin.
Rollback command is: mv -f /etc/mail/spamassassin/blacklist-uri.cf
/etc/mail/spamassassin/RulesDuJour/sa-blacklist.current.uri.cf.2; mv -f
/etc/mail/spamassassin/RulesDuJour/blacklist-uri.cf.20051201-1019
/etc/mail/spamassassin/blacklist-uri.cf;
Lint output: [2514] warn: Backslash found where operator expected at
(eval 3485) line 1, near "com\"
[2514] warn: config: invalid regexp for rule WLS_URI_OPT_0:
m//document-records.co/i: syntax error
[2514] warn: config: warning: description exists for non-existent rule
WLS_URI_OPT_0
[2514] warn: config: warning: score set for non-existent rule
WLS_URI_OPT_0
[2514] warn: lint: 3 issues detected, please rerun with debug enabled
for more information
###################################
Trying to figure out what the issue is. I opened the current
blacklist-uri.cf, and searched for "document-records".not too hard to
find since it was at the top of the file. I commented those lines out
and ran RDJ from the command line, and came up with the same problem.
Seeing this didn't fix the problem, I ran spamassassin --lint, and it
ran without errors.
My current configuration is as follows:
rules_du_jour file is v1.27, and I commented out
#ANTIDRUG=7;
#
CF_URLS[7]="http://mywebpages.comcast.net/mkettler/sa/antidrug.cf"
# CF_FILES[7]="antidrug.cf";
# CF_NAMES[7]="Matt Kettler's AntiDrug";
#PARSE_NEW_VER_SCRIPTS[7]="${PERL} -ne 'print if
/^\s*#.*(vers?|version|rev|revision)[:\.\s]*[0-9]/i;' | sort | ${TAIL}";
/etc/rulesdujour/config
##### changed 2005.12.01 CLK
##### modified: Removed ANTIDRUG
##### Comes as part of SA 3.1
##### TRUSTED_RULESETS="TRIPWIRE ANTIDRUG EVILNUMBERS BLACKLIST_URI
RANDOMVAL BOGUSVIRUS SARE_ADULT SARE_FRAUD SARE_BML SARE_RATWARE
SARE_SPOOF SARE_BAYES_POISON_NXM SARE_OEM SARE_RANDOM SARE_HEADER_ABUSE
SARE_SPECIFIC SARE_CODING_HTML SARE_GENLSUBJ SARE_UNSUB SARE_URI
SARE_REDIRECT_POST300";
TRUSTED_RULESETS="TRIPWIRE EVILNUMBERS BLACKLIST_URI RANDOMVAL
BOGUSVIRUS SARE_ADULT SARE_FRAUD SARE_BML SARE_SPOOF
SARE_BAYES_POISON_NXM SARE_OEM SARE_RANDOM SARE_HEADER_ABUSE
SARE_SPECIFIC SARE_CODING_HTML SARE_GENLSUBJ SARE_UNSUB SARE_URI0
SARE_REDIRECT_POST300 SARE_OBFU SARE_SPAMCOP_TOP200";
SA_DIR="/etc/mail/spamassassin";
SA_RESTART="/etc/init.d/MailScanner restart";
########## I started adding to list after SARE_RANDOM ################
## Here is a list of the rulesets setup below ##
## TRIPWIRE
## EVILNUMBERS
## BLACKLIST_URI
## RANDOMVAL
## BOGUSVIRUS
## SARE_ADULT
## SARE_FRAUD
## SARE_BML
## SARE_SPOOF
## SARE_BAYES_POISON_NXM
## SARE_OEM
## SARE_RANDOM
## SARE_HEADER_ABUSE
## SARE_SPECIFIC
## SARE_CODING_HTML
## SARE_GENLSUBJ
## SARE_UNSUB
## SARE_URI0
## SARE_REDIRECT_POST300
## SARE_SPAMCOP_TOP200
## SARE_OBFU
######################################################################
##################### NON AUTO-UPDATED RULES #########################
## 2005.11.21
## BACKHAIR
## CHICKENPOX
## DIVSPELLRULES
## RCDIVOBS
## ANTIDRUG (part of SA 3.1)
######################################################################
RE: Blacklist-uri.cf problem
Posted by Casey King <ck...@lovebox.com>.
...and I thank you for helping me, b/c I couldn't figure it out...I can
admit that I am not too bright. I hope you didn't feel I was being
spiteful...no reason for that...maybe all of the other events of the day
here at work are starting to get to me a little. Sorry if I came off a
bit jaded.
-----Original Message-----
From: John Narron [mailto:jnarron@cdsinet.net]
Sent: Thursday, December 01, 2005 11:29 AM
To: 'Casey King'; users@spamassassin.apache.org
Subject: RE: Blacklist-uri.cf problem
Dunno, I don't maintain it, just providing a workaround until it can be
properly fixed by the maintainer :)
John Narron | "Sacrifice, they always say
Network Administration | Is a sign of nobility
CDS/CDSinet, LLC | But where does one draw the line
http://www.cdsinet.net | In the face of injury?"
(660) 886 4045 | - Queensryche
> -----Original Message-----
> From: Casey King [mailto:cking@lovebox.com]
> Sent: Thursday, December 01, 2005 11:24 AM
> To: jnarron@cdsinet.net; users@spamassassin.apache.org
> Subject: RE: Blacklist-uri.cf problem
>
> I will definitely do this, but what happens when the update comes in
> tomorrow...will this be fixed by then?
>
RE: Blacklist-uri.cf problem
Posted by John Narron <jn...@cdsinet.net>.
Dunno, I don't maintain it, just providing a workaround until it can be
properly fixed by the maintainer :)
John Narron | "Sacrifice, they always say
Network Administration | Is a sign of nobility
CDS/CDSinet, LLC | But where does one draw the line
http://www.cdsinet.net | In the face of injury?"
(660) 886 4045 | - Queensryche
> -----Original Message-----
> From: Casey King [mailto:cking@lovebox.com]
> Sent: Thursday, December 01, 2005 11:24 AM
> To: jnarron@cdsinet.net; users@spamassassin.apache.org
> Subject: RE: Blacklist-uri.cf problem
>
> I will definitely do this, but what happens when the update comes in
> tomorrow...will this be fixed by then?
>
RE: Blacklist-uri.cf problem
Posted by John Narron <jn...@cdsinet.net>.
Seems the maintainer has already fixed this issue in version 200512011033,
so uhm.. Nevermind :)
John Narron | "Sacrifice, they always say
Network Administration | Is a sign of nobility
CDS/CDSinet, LLC | But where does one draw the line
http://www.cdsinet.net | In the face of injury?"
(660) 886 4045 | - Queensryche
> -----Original Message-----
> From: Casey King [mailto:cking@lovebox.com]
> Sent: Thursday, December 01, 2005 11:24 AM
> To: jnarron@cdsinet.net; users@spamassassin.apache.org
> Subject: RE: Blacklist-uri.cf problem
>
> I will definitely do this, but what happens when the update comes in
> tomorrow...will this be fixed by then?
>
RE: Blacklist-uri.cf problem
Posted by Casey King <ck...@lovebox.com>.
I will definitely do this, but what happens when the update comes in
tomorrow...will this be fixed by then?
-----Original Message-----
From: John Narron [mailto:jnarron@cdsinet.net]
Sent: Thursday, December 01, 2005 11:15 AM
To: 'Casey King'; users@spamassassin.apache.org
Subject: RE: Blacklist-uri.cf problem
In sa-blacklist.current.uri.cf, edit line 16:
uri WLS_URI_OPT_0 m/\b//document-records.com\b/i
to look like:
uri WLS_URI_OPT_0 m/\b\/document-records.com\b/i
If you have any sa-blacklist.current.uri.cf.<number> files, delete those
and re-run RDJ
John Narron | "Sacrifice, they always say
Network Administration | Is a sign of nobility
CDS/CDSinet, LLC | But where does one draw the line
http://www.cdsinet.net | In the face of injury?"
(660) 886 4045 | - Queensryche
________________________________
From: Casey King [mailto:cking@lovebox.com]
Sent: Thursday, December 01, 2005 10:42 AM
To: 'SpamAssassin Users'
Subject: Blacklist-uri.cf problem
As of this morning (aproximately 6:30am up to now.) all three of
my systems have failed to update RDJ. This is what I am getting as an
error.
Rules Du Jour Run Summary:RulesDuJour Run Summary on wks-lin9:
William Stearn's URI blacklist has changed on wks-lin9.
Version line: #sa-blacklist.uri: 200512010914
***WARNING***: spamassassin --lint failed.
Rolling configuration files back, not restarting SpamAssassin.
Rollback command is: mv -f
/etc/mail/spamassassin/blacklist-uri.cf
/etc/mail/spamassassin/RulesDuJour/sa-blacklist.current.uri.cf.2; mv -f
/etc/mail/spamassassin/RulesDuJour/blacklist-uri.cf.20051201-1019
/etc/mail/spamassassin/blacklist-uri.cf;
Lint output: [2514] warn: Backslash found where operator
expected at (eval 3485) line 1, near "com\"
[2514] warn: config: invalid regexp for rule WLS_URI_OPT_0:
m//document-records.co/i: syntax error
[2514] warn: config: warning: description exists for
non-existent rule WLS_URI_OPT_0
[2514] warn: config: warning: score set for non-existent rule
WLS_URI_OPT_0
[2514] warn: lint: 3 issues detected, please rerun with debug
enabled for more information
RE: Blacklist-uri.cf problem
Posted by John Narron <jn...@cdsinet.net>.
In sa-blacklist.current.uri.cf, edit line 16:
uri WLS_URI_OPT_0 m/\b//document-records.com\b/i
to look like:
uri WLS_URI_OPT_0 m/\b\/document-records.com\b/i
If you have any sa-blacklist.current.uri.cf.<number> files, delete those and
re-run RDJ
John Narron | "Sacrifice, they always say
Network Administration | Is a sign of nobility
CDS/CDSinet, LLC | But where does one draw the line
http://www.cdsinet.net | In the face of injury?"
(660) 886 4045 | - Queensryche
________________________________
From: Casey King [mailto:cking@lovebox.com]
Sent: Thursday, December 01, 2005 10:42 AM
To: 'SpamAssassin Users'
Subject: Blacklist-uri.cf problem
As of this morning (aproximately 6:30am up to now.) all three of my
systems have failed to update RDJ. This is what I am getting as an error.
Rules Du Jour Run Summary:RulesDuJour Run Summary on wks-lin9:
William Stearn's URI blacklist has changed on wks-lin9.
Version line: #sa-blacklist.uri: 200512010914
***WARNING***: spamassassin --lint failed.
Rolling configuration files back, not restarting SpamAssassin.
Rollback command is: mv -f /etc/mail/spamassassin/blacklist-uri.cf
/etc/mail/spamassassin/RulesDuJour/sa-blacklist.current.uri.cf.2; mv -f
/etc/mail/spamassassin/RulesDuJour/blacklist-uri.cf.20051201-1019
/etc/mail/spamassassin/blacklist-uri.cf;
Lint output: [2514] warn: Backslash found where operator expected at
(eval 3485) line 1, near "com\"
[2514] warn: config: invalid regexp for rule WLS_URI_OPT_0:
m//document-records.co/i: syntax error
[2514] warn: config: warning: description exists for non-existent
rule WLS_URI_OPT_0
[2514] warn: config: warning: score set for non-existent rule
WLS_URI_OPT_0
[2514] warn: lint: 3 issues detected, please rerun with debug
enabled for more information