Bug 4141 - Cannot disable SPAMCOP reporting
Summary: Cannot disable SPAMCOP reporting
Status: RESOLVED WORKSFORME
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamassassin (show other bugs)
Version: 3.0.2
Hardware: PC Linux
: P5 normal
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-15 16:27 UTC by Ken Bass
Modified: 2005-02-15 07:41 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 Ken Bass 2005-02-15 16:27:49 UTC 
There needs to be a 'use_spamcop' directive available allow override of SPAMcop.

Conf.pm should be modified to add a 'use_spamcop' config option.
Next Reporter.pm 'is_spamcop_available()' subroutine should be modified to
return FALSE if it is disabled. This is how it is done for razor, dcc, pyzor.

I'm getting a 'taint' on IO::Socket due to spamcop and there is no way to
disable it. That is what prompted this bug report.

While looking at the code I did find a workaround of adding a 
'score RCVD_IN_BL_SPAMCOP_NET 0' to my user prefs. However wouldn't a
'use_spamcop' directive be more consistent?
Comment 1 Justin Mason 2005-02-15 16:40:21 UTC 
fwiw, SA 3.1.0 has the Spamcop reporting in a plugin; as such, removing the code
is a matter of simply commenting the line in "init.pre".
Comment 2 Daniel Quinlan 2005-02-15 16:41:45 UTC 
In 3.1, administrators will be able to comment out the loadplugin line for the
SpamCop.pm plugin to disable it, achieving the same effect.  I don't think a
use_spamcop directive is needed.

It would be helpful for you to test out the current development version to
see if the taint error occurs for you and report that as a separate issue if
it does.