http://bugzilla.spamassassin.org/show_bug.cgi?id=3621
------- Additional Comments From [EMAIL PROTECTED] 2004-07-21 10:22 ------- Subject: Re: add SpamCop reporting > In my experience the Spamcop web servers are pig slow at almost any time of > day or night, and it isn't unusual to have to try 2-3 times per message to > get past timeouts before you can get to the page to validate the spam and go > on th the next one. This is a SpamCop issue, not a SpamAssassin issue. If SpamCop is overloaded, the right place to ask about it is SpamCop. I don't think we want to design around that issue. I'll talk to Julian about some of these issues, but SpamAssassin is the wrong place to address them. > a) Don't report spam below score XXX.X to Spamcop, with a default > score of maybe 40-60. No way, if it's already being caught by SpamAssassin, then there's no benefit to other SpamAssassin users in reporting it (and probably little benefit to the average person because a spam with a score of 40 or 60 will be listed in multiple DNSBLs, have sky-high Bayes scores, and so on). > b) Don't report more than XXX spam per hour, or per 24 hours. Eeck, no way do we want to worry about how many spams we've reported. That involves keeping state around on the disk or in a SQL database, additional code, etc. I think this is also something that could be more easily addressed at SpamCop. For one thing, if you've already manually verified them, then they don't need to be rechecked at SpamCop. Maybe Julian can provide a "ack all spams" button for registered user reports submitted via SpamAssassin. This discussion is out of scope for this bug, though. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
