A.Omer Koker wrote:
> Follow up with people at spamcop.  More info at
> http://www.spamcop.net/bl.shtml .  They will give you a good idea of the
> offending message and if you do nag them enough they'll remove you from
> their hole.  However spamcop is susceptible to people complaining with
> NON-spam but from people who just don't like what you might have said or
> students who don't like you ;)

We got on their list for unspecified reasons. Numerous queries to the 
people at spamcop brought no response. While spamcop may be a useful 
service. The web page you mention is useless is diagnosing the 'problem'.

This line is great - "spam traps are secret, no reports or evidence are 
provided by SpamCop"

Our advice to folks who are complaining about spamcop blocking our site 
has been to complain to their local mail admins about relying on spamcop 
for blocking mail. We use spamcop as part of a scoring system for spam 
that determine delivery but never rely on a single system (esp one we 
don't control) for blocking mail. I'm amazed that anyone does.

	al

> 
>> -----Original Message-----
>> From: LISTSERV site administrators' forum 
>> [mailto:[log in to unmask]] On Behalf Of Michael Loftis
>> Sent: Monday, February 27, 2006 4:46 PM
>> To: [log in to unmask]
>> Subject: Re: Spamcop Problem
>>
>> --On February 27, 2006 5:47:02 PM -0600 Chris Simon 
>> <[log in to unmask]>
>> wrote:
>>
>>> I'm just checking to see if anyone else has had any run-ins with 
>>> Spamcop in the past (or currently).  It turns out that 
>> messages from 
>>> listserv.nodak.edu have been caught in their spam traps and 
>> we've been 
>>> blacklisted 10 times in the last 107 days.  If you have encountered 
>>> this, what was your solution or plan of action?
>>>
>> The problem here is usually, non-confirmed dirty lists.  
>> people are added, often from marketing/for marketing 
>> purposes, *or* outright web scraped. 
>> About all you can do is try to figure out which of these are 
>> dirty and get them fixed.  Also making sure the web forms 
>> aren't being attacked/hammered (we ran into this just 
>> recently) and making sure your WHOIS registered abuse contact 
>> is responsive.
>>
>> P.S.  -- I run UNIX-WIZ on said machine.
>>

-- 

Al Lilianstrom
CD/CSS/CSI
[log in to unmask]