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





------- Additional Comments From [EMAIL PROTECTED]  2004-07-20 20:14 -------
Subject: Re:  add SpamCop reporting

> If you do use this patch for your SpamCop reports, your feedback, positive
or
> negative, would be appreciated here.

I haven't tried this patch, although I do have a spamcop reporting address.
However, I'll give a comment anyway.

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 has two effects:

a) It makes reporting more than 20-30 spams painful in the extreme; it isn't
unusual to have to spen 2-3 MINUTES of human time PER SPAM to ack the
reports with the way Julian's servers respond.  After an hour or so wasted
per day you lose interest exponentially.  I found that my tolerance limit
varied with the speed of his servers, but was usually around 15-30 spams per
day, then I would bitbucket the rest.

b) The occasional FP that slips through you might not end up catching until
after you ack the message, because you are just so damn happy that you
finally got the button for another ^&*() spam and you can report it.  You
just don't pay that much attention to reading 120 lines of spam report per
message to validate it when you are multiplexing three tasks and only
looking at the page on Julian's server every minute or two to see if the
page timed out again or finally came up.

As a result of both of these phenomona, I'd *STRONGLY* suggest having one,
or probably two, cutoff limits that the user can set:

a) Don't report spam below score XXX.X to Spamcop, with a default score of
maybe 40-60.

b) Don't report more than XXX spam per hour, or per 24 hours.

The idea here is to limit spam reports to something that you will be able to
manually verify on Julian's servers in something under an hour or two of
time per day.  If you have 400 spams to ack, or 40,000 spams to ack, it is
going to take you far longer than the 3-day timeout on spam reporting.

The idea is also to have a high enough cutoff limit that the chance that you
will inadvertantly ack an FP will be vanishingly small.

Mind you, I like the overall idea a great deal.  But I think the realities
of the time it takes to manually process each spam on the SpamCop server has
to limit the reporting to the most eggregious cases, or it won't get used at
all.

        Loren





------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

Reply via email to