Somehow the vmsperl mailing list got into the spamcop.net list.
(reason: 530 5.7.1 Blocked -
see http://www.spamcop.net/bl.shtml?63.238.179.181:Since this is a closed list, the only possibilities are:
1. The host had a security problem. (I really do not think that is likely)
2. One or more subscribers on the mailing list accidentally
reported something from the mailing list as spam, and
also confirmed that the mail list server was the source
of the spam as a second step.The second is more likely, so please be careful. Spamcop rules specifically only allow mailing list administrators to report spam that comes from a mailing list.
Now I do not know how many mailing lists share this server, so the report may not have been from a subscriber to this mailing list.
Most of the time the spamcop.net used to figure out that the mailing list was not the source, however spammers found ways to take advantage of that.
So now spamcop.net is phasing over to a mailhost configuration. If your spamcop.net account has been converted to the mailhost configuration, then if you report a mailing list message as spam, the parser will
probably stop at the mail server and indicate it as the spam source.
If the one of the mailing list administrators gets a spamcop.net account, and registers the mailing list server as one of their mailhosts, the spamcop.net parser is more likely to treat it as a trusted sender if someone accidentally reports spam in the past.
Also, if you are a SpamAssasin user, and not yet on SpamAssasin 3, reports that I seen from the field is that SpamAssasin 3 is far more accurate than the earlier versions if you use the feature that checks the I.P. address of URLs in messages against the DNSbls.
Thanks, -John [EMAIL PROTECTED] Personal Opinion Only
