Gordo,

All dnsbl's have their own procedures for removal.  Some, have no way to communicate with at all and you should not use those lists.  Your best bet is to point your customers to the site that blocked them.

My real reason for answering you post, however, is to STRONGLY suggest that you DO NOT use spamcop in your mail server.  Spamcop blocks statistically, arbitrarily, and in some cases, for no good reason at all.  Also, there is no way to get off the spamcop list except to wait for it to "time out" . Besides all that, they do not do any verification that a site they are blocking, really is a "Spam" site or an Open Relay.  The fastest way to get on their list is to have one of your customers get the Klez virus.  The client machine will suddenly send out a flood of bogus messages, the client will then fix their machine but in the meantime, YOUR smtp server is now on the spamcop dnsbl with no way to get off it.  We have seen this over and over.

The lists I use, in order, are:

dnsbl.njabl.org   (contains several other VERIFIED lists)
blackholes.easynet.nl     (Also contains several other VERIFIED lists)
relays.osirusoft.com   (We are thinking of dropping this one because the above lists account for 99.3% of our dnsbl blocks.  Only an additional  0.7% fall through to osirusoft)

 

After handling close to 2 million messages, we have had ZERO complaints of dnsbl blocks that were invalid.

 

Regards,

Dan S