>Hi, I'm using the 1.31 Beta of JunkMail standard and having fairly good
>luck identifying spam with the WEIGHT tests. I've been expecting to see
>some results from SPAMCOP as well, but have not seen a single positive
>from SPAMCOP in the logs over a period of three weeks or more, even where
>it seems clear that a positive should be expected. For example, a message
>from opt25.edirectnetwork.net [209.213.220.197] triggers a positive at
>SPAMCOP using the spam database lookup at http://www.dnsstuff.com/. But
>Declude did not catch this with the SPAMCOP test.
If an entry is listed in a spam database such as SPAMCOP, Declude should
catch it.
>SPAMCOP ip4r bl.spamcop.net 127.0.0.2 8
> 0
That is correct.
You can check to make sure that the DNS settings are correct by going to a
command prompt, and typing:
nslookup 197.220.213.209.bl.spamcop.net
You should see something like "Address: 127.0.0.2". If you see an error
message, it would indicate a DNS problem of some sort.
-Scott
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". You can E-mail
[EMAIL PROTECTED] for assistance. You can visit our web
site at http://www.declude.com .
