> That's been part of the problem. They are all independent with > their own rules, and you never know which ones the other ISPs > are using. We almost lost a MAJOR client about two years ago until > we could provide proof to them that the problem was the fault of > their client's ISP, and it's use of a blacklist server that refused > to remove any entry until it's been on the server for 30 days.
Yup, perfect example of bad RBS with a bad sysadmin to boot. Causing undue trouble with customers is very lame. > We also had to prove that we pleaded with the ISP in question > to either statically allow us, or stop using that blacklist so our > clients could communicate. Their simple response of, "Close your > relay and get off the blacklist." was both arrogant and misguided. Again, a perfect example of a bad RBL. Also, the ISP should have been responsive enough to allow your network through without the RBL check since a problem had been identified.... > In the end we saved our client, they sent all of the information > we provided to their client, and now we have both as happy customers. > > The ISP in question eventually dropped the blacklist idea, and the > blacklist they were using has since disappeared. (threats of lawsuits > I think..) As long as you are attempting to filter spam there is always a chance of false positives. I would not use a RBL that was this bass-ackwards. Good RBL's though are very effective at blocking only junk mail. > Basically there are some good ones, and way to many bad ones. Yes it > is important to notify e-mail server administrators that their server > is being used as an open relay, but the tactics used are very unnecessary > and cause more harm than good. Open relays can be solved much more > diplomatically by notifying the administrator, and including a few links > on how to go about protecting their own server. I agree; the purpose should be to fix the server and prevent spam. Not cause grief and trouble. ORDB.org is an example of a good RBL. They allow people to submit servers that are supposedly an open relay, then before it is added they actually send THEMSELVES a "junk mail" through the supposed open-relay. At this time if they were actually able to send it to themselves then they add that server to the list. If not... well then they do not :-). Once a server is added the sysadmin does not even have to fix the problem (although most do :-). All they have to do is send an email to ordb and request to be removed from the list. This usually takes less than one day (at least a few months ago this is how it read and is what I have heard from other people in another list...) ordb even shows you the headers where they successfully sent the junk mail through the open relay to themselves!! I personally do not use aggressive RBL's or block other entity's other than using good/ responsive RBL'S and other effective spam blocking tactics; and even as a very small ISP we block over 25,000 junkmails on a weekly basis. We have had 2 false positives in two years. Each were on a yahoo mail list where the advertiser had also used spam as a marketing tool. Junk mail is a very real problem that, just like bad RBL's cause customer issues and other problems. However, using an effective RBL is one of the best anti-spam tools you can choose. Of course there are several more tools that when used together with effective RBL's can drastically reduce the amount of junkmail your customers receive. Take care, Lewis The PART-15.ORG smartBridges Discussion List To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe smartBridges <yournickname> To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe smartBridges) Archives: http://archives.part-15.org
