SpamCopURI not working, was RE: More Messed Up www URLs

["Stewart, John" <jo...@artesyncp.com>]

> On Friday, May 6, 2005, 3:23:56 PM, John Stewart wrote:
> > I upgraded just the other day (at which point I suspect I 
> broke something)
> > as I saw on a site somewhere that 2.6.3 was vulnerable to a 
> DOS attack. I
> > upgraded to 2.6.4 for SA, and 0.25 for SpamCopURI
> 
> > Grepping through my messages file, it looks like the only 
> URI_RBL rule I've
> > seen triggered is SPAMCOP_URI_RBL; none of the others have 
> been triggered at
> > all.
> 
> There should be lots of hits on the other SURBL rules too.
> Probably you have contradictory installation/conf dirs or
> something similar.  Recall that SpamCopURI is technically a
> patch and should be installed after SA, so SpamCopURI can
> patch SA.

Hmmm... I just re-installed SpamCopURI 0.25. Still the same deal. Also tried
upgrading Net::DNS, but still no hits on the email containing this bad URL.

I am running an old perl... 5.6.0. Perhaps is it critical to be running
5.8.2?

The older SpamCopURIs seemed to work quite well for me... 0.14 I think was
doing nicely with SA 2.6.3. Now I've borked up the whole thing (a LOT more
spam is getting through without SpamCopURI working).

I've had on my project list for a LONG time to completely rebuild our spam
scanner, but I just don't have the time right now... so if anyone has any
suggestions on things to get this box working more or less intact, I'm all
ears. 

thanks!

johnS

Re: SpamCopURI not working, was RE: More Messed Up www URLs

[Jeff Chan <je...@surbl.org>]

On Monday, May 9, 2005, 8:50:43 AM, John Stewart wrote:
> Hmmm... I just re-installed SpamCopURI 0.25. Still the same deal. Also tried
> upgrading Net::DNS, but still no hits on the email containing this bad URL.

> I am running an old perl... 5.6.0. Perhaps is it critical to be running
> 5.8.2?

> The older SpamCopURIs seemed to work quite well for me... 0.14 I think was
> doing nicely with SA 2.6.3. Now I've borked up the whole thing (a LOT more
> spam is getting through without SpamCopURI working).

> I've had on my project list for a LONG time to completely rebuild our spam
> scanner, but I just don't have the time right now... so if anyone has any
> suggestions on things to get this box working more or less intact, I'm all
> ears. 

Have you tried spamassassin -D < some_message and spamassassin
--lint?

Jeff C.
-- 
Jeff Chan
mailto:jeffc@surbl.org
http://www.surbl.org/