I've always been a bit leery of dnsbl's (DNS-based Blocking Lists), as they tend to take a very aggressive, baby with the bathwater approach to preventing spam, but have always considered them a necessary evil in the fight against spam (I HATE SPAM!).
My mind is changing now though, for the worse.
The fucking moron(s?) at SORBS decided on friday or so to just add pretty much the entire /16 the ISP I work at runs on to their blocking list because much of the rdns for the IPs contains the word "PPP".
PPP DOES NOT MEAN DYNAMIC, DIPSHIT! It's a fucking encapsulation protocol that has the benefit of being open and standards-based and highly flexible. Having PPP on a circuit has NOTHING to do with whether an IP on that circuit is dynamic or nut.
But no, instead of investigating and doing some due diligence, this nimrod just decides, "Heck, let's make it so none of the 65,000 IP addresses in this block can send email to anyone using my list... yeah... I'm so smart!"
Dipshit. Respond to your fucking support emails already...
Posted by Campbell at April 7, 2004 09:27 AMWhat's the /16 that got blacklisted? I'd like to see if it's blacklisted anywhere else in order to determine if the ISP you work for is spam-friendly or anti-spam (or just sitting on the fence like many wish to remain).
Posted by: Randolf at June 9, 2004 03:02 PMActually, the ISP I work for is extremely diligent about prosecuting spam (and worm traffic) related complaints.
I know this because I'm the guy who primarily handles all abuse complaints, and we respond vigorously to complaints by blocking the customer's service (outbound smtp in the case of spam complaints, all traffic in the case of worm traffic) and notifying the customer directly. We don't lift the block until they have confirmed the issue is resolved. In addition, if they get so filtered three times, after the third filter, the blocked service is NEVER restored. We've lost more than a few customers that way, but I for one hate spam, and thus think it is a fair trade.
In addition, we do a daily scan of all outbound traffic from our customers, looking for patterns of traffic (sweeps on suspect ports, etc) that indicate that they have a compromised system, and work with the customer to resolve it (uncooperative customers are blocked until resolution).
Between those two steps, we have ended-up with a very clean network. Perfectly clean? Of course not, but still very clean.
I also google variations of our block every few weeks to see if anything has popped-up about it. Very little has, and what is out there is generally very old (and un-updated).
The SORBS issue has since been resolved (though it took most of two weeks), and SORBS as much as admitted that the block was arbitrary.
So, spam-friendly? HELL NO. I hate spam.
Posted by: Haleon (aka, da Authah) at June 10, 2004 12:02 AMI came to this page from google by typing:
"sorbs sucks". What authority sorbs has to block IP addresses? Their stupidity has no limits. They now block dynamic IPs, morons! They do not have even a phone number. My company will now block all sorbs fans all ISPs that use sorbs and stupid companies such as Adelphia which also block its' customers ports 25. Then, we will take this matter to a local court.
WTF! i hate those fuckers! i have the same fucking problem and now i cant send any fucking email! fucking morons! m-o-t-h-e-r-f-u-c-k-e-r-s!
Posted by: asdads at June 29, 2004 09:45 PM