James Merrill Posted January 20, 2006 Share Posted January 20, 2006 It appears that the current version of "Quick - report immediately and trash" reporting makes no effort to look for spamvertised sites and report them. (I don't know if it ever did. I know that I was a little surprised when I noticed that.) Shutting down spamvertised sites is much more valuable, I think, than telling ISPs responsible for the mail being sent that someone on their network has an open proxy or is a Windows box that's been taken over by the bad guys. I want to shut down the spamvertised sites, so that the people who run them stop thinking that it's so close to free to send a gazillion spams. I understand SpamCop not wanting to do the spamvertised-site reporting automatically. However, it takes a _lot_ more time to report spams manually than to quick-report them, largely because we have to wait for the parsing (though some of it is checking the appropriateness of the spamvertised site analysis and waiting for the reports to be generated). How about changing the behavior of "queue for reporting"? Now, when I go to the "Report spam" page and click "Unreported spam Saved: Report Now" I have to wait for them to be parsed one at a time, and the parsing is distinctly not instantaneous. I suggest that "queue for reporting" change (internally) to "queue for parsing" so that when I go to "report unreported spam" the already-parsed results are shown. (There would have to be a re-parse button in case I want to do that, and of course if there aren't any already-parsed results ready it would do a live parse.) That would reduce the waiting time for me to report the spams manually and thus hit the owners of spamvertised sites. In the implementation, some type of daemon task could throw away parse results that are more than 30 mins or 1 hour old. The queued parsing could run at a lower priority than live parsing (possibly running on older, slower, not-quite-recycled machines); that could improve response time for live parsing (by spreading out the parsing effort) while reducing see-parse-results wait time for people who are reporting many spams manually. This doesn't seem to me to be a particularly difficult thing to implement, and it offers significant benefits to SpamCop and not just its users. Thanks for listening. Link to comment Share on other sites More sharing options...
This topic is now archived and is closed to further replies.