Along the same lines of Senderbase that I was talking about earlier, I've noticed that a lot of good email is getting stuck by DNSBL scoring simply because an email is considered Bulk. For Example: X-Assp-Score: 42 (DNSBL: neutral, 63.111.28.63 listed in blackholes.five-ten-sg.com ix.dnsbl.manitu.net) X-Assp-DNSBL: neutral, 63.111.28.63 listed in (blackholes.five-ten-sg.com<- rm02 net bulk ; ix.dnsbl.manitu.net<-127.0.0.2; ) This is just one example out of many. Just because it is considered "Bulk", to me, doesn't necessarily mean it's bad. The email is called Popular Woodworking and is completely legit. So, what I end up doing is adding 63.111.28.0/24 to the noRBL.txt file. That's ok for every once in a while, but this happens quite frequently for good "bulk" email and gets to be a chore adding blocks of IP Addresses to the noRBL.txt file. I am using the default RBLServiceProvider list and am now at 1.5.1.2 (1.0.0). I keep an eye on spam that gets caught, but I want to be able to look away for a few days without having to worry about checking my ccspam folder. Is there perhaps a better way I can manage this? Kind Regards, Brett ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
