[SpamCop-List] Re: SpamCop Painfully Slow

[Mike Easter]

Paul D wrote:
> I'm finding that reporting Spam to SC, or even just browsing the
> website, has become unusably slow.

That's a hard problem to diagnose.  Someone else is reporting that too,
but I'm not seeing it.

> To be honest, I don't believe it's routing or latency of hops, but
> the SC website itself.

I don't think it is the route or hop latency either, but I don't know
what the problem is for you.

> By the way, could you clarify how many reports from different people
> is required about a particular piece of Spam before Spamcop considers
> the report legitimate?

A report's 'legitimacy' as to being a spam is established by the fact
that you, a SC reporter is reporting it.  The purpose of the parser
reporter is to determine the source IP address and to notify the
appropriate provider for that IP and also to contribute that source IP
to the spamcop blocklist which is derived from a formula described here
http://www.spamcop.net/fom-serve/cache/297.html What is the SpamCop
Blocking List (SCBL)?

The other function of the parser reporter is to determine spamvertised
site notify addresses and to notify those providers of the SC report, so
that they can act on that information according to their wishes.  The
only consequence of being a spamvertiser in a SC report is that SC
publishes those on its statistics page, and a separate listing service
surbl scrapes those spamvertised URLs from the statistics page and uses
them for its own listing functions.

> Even though I have managed to successfully
> report spam before, Spam status of these emails does not change in my
> client.

How your client recognizes spams and what an individual items
characteristics are will determine whether or not your client identifies
an item as spam or not.


-- 
Mike Easter
kibitzer, not SC admin