QUOTE(ahmedsm @ May 10 2008, 09:51 PM)

I have configured the Anti-spam option in the hub transport and provided the DNS suffix bl.spamcop.net as given in the FAQs but i got an error message saying that bl.spamcom.net isn’t a valid DNS suffix, i substituted it by spamcop.net simply, i don’t know if this is a right configuration to acquire block lists directly from spamcop.
See Don's post above. You can verify (nslookup from Windows command line) like - for ISP 118.169.192.241 which won't necessarily be listed when you look -
Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.
C:\xxx>nslookup
***
***
Default Server: x
Address: x
> set type=txt
> 241.192.169.118.bl.spamcop.net
Server: x
Address: x
Non-authoritative answer:
241.192.169.118.bl.spamcop.net text =
"Blocked - see
http://www.spamcop.net/w3m?action=checkblo...9.192.241">
If not listed the answer is like
*** UnKnown can't find 241.192.169.118.bl.spamcop.net: Non-existent domain
Which is sort of inconclusive, find a new IP (and reverse it for lookup) from
http://www.spamcop.net/w3m?action=hoshame - pick one near the top, reported for a few hours to maximize chance of being listed
[on edit - SCbl lookup page changed to initial lookup which is not the actual txt value but more useful in this context]