3.3.0 local.cf parse error

2010-01-27 Thread Jackson, Jeff
I'm getting the following parse errors after upgrading to 3.3.0:

Jan 27 08:04:15.172 [30437] warn: config: failed to parse line, skipping, in 
/etc/mail/spamassassin/local.cf: use_auto_whitelist 1
Jan 27 08:04:15.172 [30437] warn: config: failed to parse line, skipping, in 
/etc/mail/spamassassin/local.cf: auto_whitelist_factory 
Mail::SpamAssassin::SQLBasedAddrList
Jan 27 08:04:15.173 [30437] warn: config: failed to parse line, skipping, in 
/etc/mail/spamassassin/local.cf: user_awl_dsn DBI:mysql:spamassassin
Jan 27 08:04:15.173 [30437] warn: config: failed to parse line, skipping, in 
/etc/mail/spamassassin/local.cf: user_awl_sql_username amavis
Jan 27 08:04:15.173 [30437] warn: config: failed to parse line, skipping, in 
/etc/mail/spamassassin/local.cf: user_awl_sql_password spamdb
Jan 27 08:04:15.173 [30437] warn: config: failed to parse line, skipping, in 
/etc/mail/spamassassin/local.cf: use_dcc 1

I've got two, previously, identical servers setup, one produces these errors 
with a spamassassin -D --lint command, the other doesn't, the local.cf files 
are identical, to the point that I've copied the working server's local.cf to 
the non-working server. Still get the errors. Any ideas why one server would 
have the errors and the other not? Prior to upgrading, I wasn't getting any 
errors with 3.2.5...

Jeff


RE: Fuzzyocr and rule errors after upgrade to 3.3.0

2010-01-27 Thread Jackson, Jeff
Thank you guys! I'm now down to just 5 non-existent rule warnings as well:

Jan 27 10:18:13.473 [19398] dbg: config: warning: score set for non-existent 
rule SHORTCIRCUIT
Jan 27 10:18:13.473 [19398] dbg: config: warning: score set for non-existent 
rule SUBJ_RE_NUM
Jan 27 10:18:13.473 [19398] dbg: config: warning: score set for non-existent 
rule FM_VIAGRA_SPAM1114
Jan 27 10:18:13.473 [19398] dbg: config: warning: score set for non-existent 
rule AXB_HELO_LH_HOME
Jan 27 10:18:13.474 [19398] dbg: config: warning: score set for non-existent 
rule ACCESSDB

I presume we are all missing the same rules...

Jeff

-Original Message-
From: John Wilcock [mailto:j...@tradoc.fr] 
Sent: Wednesday, January 27, 2010 10:03 AM
To: users@spamassassin.apache.org
Subject: Re: Fuzzyocr and rule errors after upgrade to 3.3.0

Le 27/01/2010 18:57, Justin Mason a écrit :
 Either someone forgot to delete all these rules, or (more likely IMO)
 someone forgot to include 72_active.cf and 80_additional.cf in the sa-update
 files.

 I think you're dead right.  It appears one of the build scripts does
 the wrong thing with the 3.3.0 release, and cut an update missing
 those files. :(

 I've just cut a new update which should fix it, and opened a bug to
 fix the build procedure...

sa-update has now pulled down a 72_active.cf file, and lint now only 
gives 5 score set for non-existent rule warnings instead of 463.

Thanks Justin.

John.

-- 
-- Over 4000 webcams from ski resorts around the world - www.snoweye.com
-- Translate your technical documents and web pages- www.tradoc.fr


Insecure dependency error w/ SA 3.0x when reporting to spamcop

2004-11-09 Thread Jackson, Jeff
Hello,

I did some archive searching and while I saw references to this error, I
didn't see any solutions. So, in great hope, here I go...

The server is RH9, kernel 2.4.20-31.9. SpamAssassin is 3.0.1.

When I report spam using spamassassin -r -D, at the end of the output, I
see this error:

debug: Razor2: spam report, response is 1.
debug: leaving helper-app run mode
debug: SpamAssassin: spam reported to Razor.
1 message(s) examined.
Insecure dependency in connect while running with -T switch at
/usr/lib/perl5/5.
8.0/i386-linux-thread-multi/IO/Socket.pm line 114.

I thought it was a Razor problem at first, but as you can see, Razor
reports fine. I now believe this is occurring when reporting to spamcop.
Then main reason is, I was reporting some messages yesterday that had
accumulated over the weekend. Instead of the

Insecure dependency in connect while running with -T switch at
/usr/lib/perl5/5.
8.0/i386-linux-thread-multi/IO/Socket.pm line 114. 

error, I was getting an error telling me something to the effect that
the message was to old and wouldn't be reported to spamcop. That's when
I realized is wasn't Razor. Is there a way to disable reporting to
spamcop? I haven't been able to find anyway to do it.

Or better still, can anyone shed any light on why reporting to spamcop
might give me this error?

Jeff


error loading ClamAV.pm

2004-11-09 Thread Jackson, Jeff
 This is my first Perl code ever, so be gentle. ;-) The code is public 
 domain, do whatever you like with it. Note that it requires 
 File::Scan::ClamAV.

http://search.cpan.org/%7Ecfaber/File-Scan-ClamAV/lib/File/Scan/ClamAV.p
m

I'm getting an error when I try to load the plugin:

debug: plugin: loading File::Scan::ClamAV from
/etc/mail/spamassassin/ClamAV.pm
Reference found where even-sized list expected at
/etc/mail/spamassassin/ClamAV.
pm line 119.
debug: plugin: registered File::Scan::ClamAV=HASH(0x8df57f8)

I'm sorry to admit I'm not very perl literate. Can someone tell me what
the erron on line 119 means and how to make it go away?