SpamCopURI-0.19 seems broken

[Stephen Swaney]

> -----Original Message-----
> From: MailScanner mailing list [mailto:MAILSCANNER at JISCMAIL.AC.UK] On
> Behalf Of Jeff A. Earickson
> Sent: Monday, July 26, 2004 3:09 PM
> To: MAILSCANNER at JISCMAIL.AC.UK
> Subject: SpamCopURI-0.19 seems broken
>
> Gang,
>     I've been following the "BigEvil and Stuff" thread, and I too have
> been having
> issues with SpamCopURI-0.19, eval: complaints and open_redirect_list
> complaints.
> My setup: Solaris 9, SA 2.63, URI-1.31 (also tried 1.30), MS 4.31.6.
> And perl 5.8.4: osname=solaris, osvers=2.9, archname=sun4-solaris-thread-
> multi
>
> I downloaded Steve Swaney's version from http://www.fsl.com/support/
> and followed the instructions, including cleaning out my copies of
> backhair,
> bigevil, etc from my /etc/mail/spamassassin directory.  My lint output
> from
> "spamassassin -D -p /etc/mail/spamassassin --lint" gives garbage like:
>
> Failed to parse line in SpamAssassin configuration, skipping:
> open_redirect_list
> _spamcop_uri   snurl.com              *.snurl.com
> (etc)
>
> and
>
> Failed to compile URI SpamAssassin tests, skipping:
>      (syntax error at /etc/mail/spamassassin/surbl_uri.cf, rule
> SPAMCOP_URI_RBL,
> line 1, near "eval:"
> syntax error at /etc/mail/spamassassin/surbl_uri.cf, rule OB_URI_RBL, line
> 1, ne
> ar "eval:"
> syntax error at /etc/mail/spamassassin/surbl_uri.cf, rule OB_URI_RBL, line
> 9, ne
> ar "}
>      }"
> )
>
> Following the advice of the list, I commented out the open_redirect lines,
> and
> removed the "eval:" stuff in surbl_uri.cf to shut up these complaints.
>
> However -- I'm not convinced that this is the correct fix.  I did this on
> Friday
> night and I got a TON of spam over the weekend.  Way more than usual.
> Methinks
> SpamCopURI-0.19 is useless, or neutered by the changes to surbl_uri.cf.
>
> How to *really* fix these errors???
>
> Jeff Earickson
> Colby College
>

Jeff,

I wish I could help but I can't repeat your problem. The files install and
run fine on almost all systems. Only a few appear to complain. Probably some
obscure difference in spam assassin installation or installed per modules or
perl version.

What is your perl version? If it's an older version this might be the
problem since SpamAssassin 3.0 will not support older versions of perl and
this is a feature that built into SpamAssassin 3.0 and back-ported to 2.63

Also it might help if you posted this problem to the surbl-discuss list you
might get an answer. They are petty good at responding.

Steve

Stephen Swaney
President
Fortress Systems Ltd.
Steve.Swaney at FSL.com




--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Fortress Systems Ltd.
www.fsl.com

-------------------------- MailScanner list ----------------------
To leave, send    leave mailscanner    to jiscmail at jiscmail.ac.uk
Before posting, please see the Most Asked Questions at
http://www.mailscanner.biz/maq/     and the archives at
http://www.jiscmail.ac.uk/lists/mailscanner.html