Re: spamcop

["s. keeling" <keeling@spots.ab.ca>]

Kamaraju Kusumanchi <kamaraju@bluebottle.com>:
>  On Saturday 30 September 2006 12:02, Andrew Vaughan wrote:
> > My phrasing evidently wasn't clear.  AIUI the problem isn't misdirected
> > confirmation emails.  The problem is that some spam makes it through debian
> > filters.  List subscribers then report that that spam to spamcop.  Spamcop
> > then blames murphy for sending that spam.
> 
>  Spamcop will list an IP address based on two criterion
> 
>  1) mails sent to spamtraps
>  2) mails reported by users as spam

SC also takes into account the number of separate reports from
discrete users.  One report means little.

In the past, when I was receiving list mail, I've reported spam
received from the list and the Spamcop report always mentioned that it
noticed the spam came from a mailing list and SC never blamed the
list.  It went after the spam's originator.  I'm always very careful
about checking who or what Spamcop is going to slap once I confirm
it's spam, and I never saw it list murphy or any other Debian machine
as being responsible.

Nowadays, I read the lists via the Usenet gateways linux.debian.*, so
I no longer have to care.  Whatever spam lands on the list doesn't get
to my eyes unless I'm dumb enough to tell slrn to display it.  If it
does, that's my fault more than anyone else's.


-- 
Any technology distinguishable from magic is insufficiently advanced.
(*)    http://www.spots.ab.ca/~keeling          Linux Counter #80292
- -    http://www.faqs.org/rfcs/rfc1855.html    Please, don't Cc: me.
       Spammers! http://www.spots.ab.ca/~keeling/emails.html