You could comment out the "spamcop_to_address" in your configuration file. Then SA will report to the "generic" spamcop address. Your reports won't be given as much weight (whatever that means) but you won't get the confirmation emails either.
L -----Original Message----- From: Nix [mailto:[EMAIL PROTECTED] Subject: Sensible way to use SpamCop reporting? I installed SA 3.0 (from SVN branch head) last night and found to my displeasure that it automatically reported all my spams to SpamCop. Rather, that was fine: the downside was that SpamCop bombed me with one email per spam reported, and required manual verification of every single one. Am I the only one who finds this makes SpamCop reporting nigh totally useless? I've *already* verified that things are spam before feeding them to `spamassassin -r': reading (rather, ditching) an email telling me something I already know and wandering through a webform to verify it, well, this takes orders of magnitude longer than reading the damned spam would have done to start with! (And with >1000 spams a day, well, the stuff comes in faster than I could verify them by hand in any case.) I suppose the ideal would be to tell SpamCop only about false negatives: but I can't see an easy way to do that with SpamAssassin yet. The source includes a `dont_report_to_spamcop' option to report_as_spam(), but nothing sets it; a switch, or an extended --report option, to specifically report (or not report) to particular reporting services would be ideal. I've temporarily removed the report-to-spamcop code from Reporter.pm to keep the mailbombing from SpamCop down; is there a better way, or is mass reporting to SpamCop a lost cause? -- `Random line noise picked up from an RS432 cable hung in front of a faulty radar transmitter. ' --- Greg Hennessy on sendmail.cf
