[Bug 4141] New: Cannot disable SPAMCOP reporting

[bu...@bugzilla.spamassassin.org]

http://bugzilla.spamassassin.org/show_bug.cgi?id=4141

           Summary: Cannot disable SPAMCOP reporting
           Product: Spamassassin
           Version: 3.0.2
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: spamassassin
        AssignedTo: dev@spamassassin.apache.org
        ReportedBy: kbass@kenbass.com


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?



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 4141] Cannot disable SPAMCOP reporting

[bu...@bugzilla.spamassassin.org]

http://bugzilla.spamassassin.org/show_bug.cgi?id=4141





------- Additional Comments From jm@jmason.org  2005-02-15 16:40 -------
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".



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 4141] Cannot disable SPAMCOP reporting

[bu...@bugzilla.spamassassin.org]

http://bugzilla.spamassassin.org/show_bug.cgi?id=4141


quinlan@pathname.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME




------- Additional Comments From quinlan@pathname.com  2005-02-15 16:41 -------
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.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.