I can't believe the *irony*! You're not going to believe this!

After fixing this problem I fed back one of my messages I had posted and subsequently received via this list into SpamAssassin as a test to see what happened. I got the following result:

 pts rule name              description
-4.9 BAYES_00               BODY: Bayesian spam probability is 0 to 1%
                            [score: 0.0000]
 0.1 RCVD_IN_NJABL          RBL: Received via a relay in dnsbl.njabl.org
                            [81.103.167.62 listed in dnsbl.njabl.org]
 0.1 RCVD_IN_SORBS          RBL: SORBS: sender is listed in SORBS
                            [81.103.167.62 listed in dnsbl.sorbs.net]
 0.7 RCVD_IN_DSBL           RBL: Received via a relay in list.dsbl.org
                            [<http://dsbl.org/listing?ip=81.103.167.62>]
 0.5 RCVD_IN_NJABL_PROXY    RBL: NJABL: sender is an open proxy
                            [81.103.167.62 listed in dnsbl.njabl.org]
 1.2 RCVD_IN_SORBS_SOCKS    RBL: SORBS: sender is open SOCKS proxy server
                            [81.103.167.62 listed in dnsbl.sorbs.net]

My current DYNAMIC ip address appears to be listed in many blacklists!

Check it here: http://www.dnsbl.info/quickcheck.asp

I'm not sure why this is - presumably because a previous owner of this dynamic ip had an open relay.

Has this caused my messages to be flagged as spam (or at least, have a bad score) for those of you that are using RBL? I'd be grateful if someone could check the headers of one of my messages (ie, this one) and send me the SA result headers/score.

This is a good example of a false positive as my IP definitely does NOT have any open relays (or even any open ports for that matter). Had it not been for the bayesian filter, my own message would have been flagged as spam.

Nick...



Reply via email to