Hackers Blamed For MessageLabs Spam Blunder 44
littlekorea writes "MessageLabs claims to have discovered that the systems of one of its customers were hacked by spammers after an entire block of MessageLabs IP addresses was blocked by antispam service SORBS. Customers of the managed email service had problems with outbound mail last week after MessageLabs' IP addresses were included in SORBS' block list. The Symantec-owned service provider has assured customers it has systems in place to prevent such incidents from happening again."
This all sounds backwards (Score:4, Informative)
Doesn't it seem much more likely that the hack is what lead to the spam being sent, THEN the site got blocked as a result?
Re:Please don't use SORBS blocklist (Score:3, Informative)
Seconded. I tried using them a few years back and balked at the appalling quality of the data.
In any case, using greylisting, some basic header sanity checking and spamhaus kills 99%+ of the spam so there is really no technical need to use such an aggressive list.
Please don't use ANY blacklist (Score:5, Informative)
In addition to the complaints specific to SORBS, here [acme.com]'s what the acme.com owner (who, more than half a decade ago, received an the order of a million spam mails per day) has to say about DNS-RBLs in his write-up on how to efficiently and effectively filter spam:
DNS-RBLs - Domain Name System Realtime Black Lists. In theory the idea is fine. You have a set of sites that you blacklist, and you want to let other folks use the same list so you distribute it using DNS, which is a nice efficient de-centralized database. What's not to like?
Well, I don't know why, but in practice every single DNS-RBL eventually comes under the control of power-hungry weenies. They start listing sites unreliably, and if you complain you find yourself listed. And there's usually no way to get off the list.
A lot of people tell me I'm wrong about this. They say that certain DNS-RBLs are ok, with objective criteria for inclusion and simple procedures for getting off the list. The thing is, they give conflicting recommendations for which lists are good and which are bad. Some of these folks recommend lists which I know from personal experience are bad.
This problem is really inherent in the way DNS-RBLs are set up. You cede control of your mail system to a third party, with no real possibility of checking how they are doing. The people running the lists get overwhelmed with bogus feedback from spammers and/or idiots, to the point where they assume all their mail about the lists is from spammers and/or idiots.
If the lists you use have not yet descended into corruption and chaos, consider yourself temporarily lucky.
Do not use DNS-RBLs.
As you can see, he addresses the specific problems with SORBS ("in practice every single DNS-RBL eventually comes under the control of power-hungry weenies. They start listing sites unreliably, and if you complain you find yourself listed. And there's usually no way to get off the list"), gives a reason for why this is ("the people running the lists get overwhelmed with bogus feedback from spammers and/or idiots, to the point where they assume all their mail about the lists is from spammers and/or idiots"), draws his conclusions ("this problem is really inherent in the way DNS-RBLs are set up. You cede control of your mail system to a third party, with no real possibility of checking how they are doing") and arrives at a recommendation ("do not use DNS-RBLs").
extortion by SORBS (Score:5, Informative)
Re:extortion by SORBS (Score:5, Informative)
Similar nightmare for a project website started awhile back. We registered with the host, a VERY BIG host I'll add, and suddenly found our assigned IP addresses were all blocked. SORBS said it was the provider's fault, they gleefully hosted spam sites so must be punished. It would sure be nice to have group related e-mail for organizational purposes. Unless our host paid to play, it was game over. No big deal, we moved to an even BIGGER, more expensive, host (currently a publicly traded company with some big 'cloud' options) and yet again found our new IP addresses blocked, oddly though, only after our domain was updated with the new DNS addresses.
It boggled the mind how a brand new, never registered previously before domain for a research project related to a small scientific group studying x-ray deep surface x-ray diffraction could be the root cause of a huge criminal enterprise. One might think SORBS took offense to a previous email relaying certain concerns and blocked the domain out of spite. Fortunately when we relayed those fears SORBS corrected us, and proved with some very convincing records that 2 chemists and a physicist were really responsible for the downfall of humanity, and all it would take is a donation to their legal fund. (Oppenheimer eat your heart out).
The advantage of toiling for a university day and night is access to a rather sophisticated legal department that loves crushing tiny people like Kevin SORBOS playing Hercules. Needless to say, the SORBS legal defense fund suddenly looked like it was going to get a real workout, and magically, an error was found and corrected. We were unblocked.
Let me say it one more time...Nightmere.