Bug 2794 - SPAM COP is all wrong
Summary: SPAM COP is all wrong
Status: RESOLVED WORKSFORME
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Rules (show other bugs)
Version: 2.60
Hardware: Other Solaris
: P5 normal
Target Milestone: 2.70
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-29 02:12 UTC by Graham Potts
Modified: 2003-11-29 00:18 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Graham Potts 2003-11-29 02:12:00 UTC 
You are using SPAM COP as one of your blacklists. Over recent weeks more and 
more legitimate email is being flagged as spam and ending up in my spam 
folder. Every time I see this it is because of a blacklisting on SPAM COP. The 
ones I found this morning were all for a legitimate list I am on and were from 
people using AOL. None of the other blacklists were listing the host involved. 
The 'real' spam from blacklisted hosts always seems to be blacklisted by more 
than one blacklist.

Why not require a host to be blacklisted by more than one list before you 
label it as spam?
Comment 1 Michel Bouissou 2003-11-29 02:50:29 UTC 
No, SpamCop isn't wrong. SpamCop has its own listing policy, and is one of the 
most efficient blacklists out there. 
 
And a SpamCop listing isn't enough by itself to make SA classify a message as 
spam. It just gives a score that is taken into account in the message scoring, 
that will ultimately determine if the message should be classified as spam or 
not. 
 
You can configure your own copy of SpamAssassin according to your own 
preferences, you can rise or lower SpamCop's BL score if you wish, or you can 
completely disable it if you prefer. So what ? 
 
Please read the documentation and don't report imaginary bugs.
Comment 2 Duncan Findlay 2003-11-29 09:18:10 UTC 
Michel, go easy on him :-)

Michel's right though. SpamCop is not necessarily right all the time, and thats
why it's not given a score big enough to mark messages as spam on its own.

If you want, you're welcome to lower the score for the spam cop tests, (read man
Mail::SpamAssassin::Conf for more info).