ORDB.org Going Offline
Allan Joergensen writes "ORDB.org has announced that they will shut down their services after fighting open relays and spam for more than five and a half years.
The RBL DNS service and mailing lists will be taken down today (December 18, 2006) and the website will vanish by December 31, 2006." The reasons given tend to be the usual ones - volunteers have been focused on other things in life; my salute to those folks for keeping the service up as long as they did.
Even though it took a long time to get my own domain off their list after I left a mis-configured server out in the wild, I really appreciate all they have done over the years. Who will take up the mantle next?
No incumbents, not no where, not no how.
Vote them out every term.
The reasons are, expanding from TFA: "open relay RBLs are no longer the most effective way of preventing spam from entering your network as spammers have changed tactics in recent years, as have the anti-spam community."
I concur.
Now if extortionist SORBS would die, the anti-spam communinity could refocus on dealing with actual spammers. SORBS never was a pillar of responsibility but the current practice of "dontate to a SORBS-approved charity to get off the list" is just plain wrong.
Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
If they've already shut down, I guess that explains the rather sudden and rather LARGE increase in spam I had sitting in my various mailboxes waiting for me this morning. :(
Can anyone suggest a good alternative? I'm using spamhaus, sorbs, and uceprotect at the moment, and no, I won't use spamcop. ordb HAD been an excellent fourth.
"I feel that if a person can't communicate, the very least he can do is to shut up." -- Tom Lehrer
If the RBLs go offline, will spammers shift back to using open relays? I suspect not; the bot-nets are harder to stop and, from the spammer's POV, probably more reliable. The dark side of distributed, highly redundant networks.
Still, it's pretty nice to think that they're going offline because they've largely solved the problem they were fighting. It's like declaring smallpox or polio extinct. And if they come back, we'll remember the formula.
I guess some of these groups have a rather large following, but how about actually linking to their page or to a wiki that describes what they do? For those of us lazy American's too lazy to cut and paste.
-Rick
"Most people in the U.S. wouldn't know they live in a tyrannical state if it walked up and grabbed their junk." - MyFirs
Thanks - that's not even two weeks notice.
More likely, they woke up one day and figured out they were sick of eating Ramen noodles while being taking for a ride by commercial leeches who never kicked back.
commercial leeches that never give back - that's why free software is dying and will NEVER work as a "business" model.
Spamassassin is great, we have sever custom rules and find it very effective. However it is resource intensive, especially if you are to add features like OCR detection of image spam.
Is it really the case that folk should be accepting all this traffic from known open relays and then spending processor cycles analyzing it?
Is there a middle ground? Some third way that lets lets you reject as much as possible at the start of the SMTP transaction? Greylisting is certainly an option but it presents significant problems too - many companies simply won't respond. Automatic emails will be missed, signup to websites becomes problematic etc etc. What, if any, are the other options?
I'm not sure I agree about the lack of efficiency: On a "normal" day my server which hosts about 60 mailboxes blocks between 5000 and 6000 e-mail messages (4992 yesterday, 4936 Sunday, 5615 Saturday, 5763 Friday etc.) using ordb, spamhaus and dsbl. While it's true that I still have to use spamassassin for additional content filtering, that's more than 5000 messages a day which don't even enter the system - I consider that quite a lot.
They did provide the service free of charge for over five years if I'm not mistaken.
Still, you have a point. The same thing happens with other community-based products. An excellent example, although it might seem a bit puerile, can be found in pretty much every video game mod forum. There is either drama, or real life, or a new game in the series comes out, and *poof*, the mod, if it even reached a downloadable version, goes out the window and people are not even given the opportunity to "take up the mantle" as the first post said.
I have to suspend my disbelief a little bit to believe that nobody on the Great Intertron was willing to do this and at least occasionally maintain ORDB as a legacy service. I do understand, of course, the necessity of promptness in removing fixed mail servers from the list, although that wasn't really very prompt in practice, was it?
I may make you feel, but I can't make you think.
According to ordb.org's website, they maintained a list of open relay servers that you can use to block mail. I may be wrong but it seems that most email servers disable open relay by default. I know that Postfix takes great pains to prevent open relay in the default install, configurations not even withstanding. ORDB filled a niche for a while but may actually be redundant at this point. Spam will always be a game of cat and mouse.
A "private" e-mail account, given only to family and close friends, whit a set of filtering rules to build the whitelist, and everything else run through bayesian filtering.
Between the two, I have to deal with very little spam.
OT:This is my 2,000th Slashdot comment...
Best Slashdot Co
The ORDB notice makes it sound like we should all abandon RBL lookups all together. I operate a small GroupWise domain ~about 300 users~ and checked my GWAVA stats when I read the article. 78,000 of the last 155,000 inbound messages were blocked as RBL hits. This first step in ridding most of our spam takes a load off of the more server intensive methods of filtering mail and still seems very relevant. I will be sad to see ORDB go.
For those of you relying on RBL lookups, the following are still available and seem to be very reliable, producing few to zero false positives:
zen.spamhaus.org
bl.spamcop.net
list.dsbl.org
Not to be a troll, but what's the breakdown per service? Is ordb doing the heavy lifting? Or is spanhaus? If it's an even 33% aross the board, ok. But if ordb is only doing 1% of that 5000 then they're right, blocking relays is no longer effective.
The simple truth is that interstellar distances will not fit into the human imagination
- Douglas Adams
Since the Republican Congress "defeated spam" with their CAN-SPAM Act, I've noticed my incoming spam double every month for years. While I notice that the antispam organizations keep folding, or even getting shut down.
--
make install -not war
I started using Blacklists, but always ended up in a mess. Stuff still got through, so you'd add another blacklist and then one would randomly start blocking gmails 'to teach google a lesson' etc.
ASSP installs nicely (I'm actually running it on MS Server with hmailserver) and does what it says on the tin. Takes a week or so to train it up, but once it's up it easily gets 99% of all spam, tags it and then my mail server shoves it into my users junk folders.
You have a point, but Free Software is hardly "dying" ! That's a ridiculous claim to make. *More* Free Software is being produced and used today than ever before. Just take a look at Freshmeat or Sourceforge.
Of course, if commercial organisations did wake up and realise they have a responsibilty to help support developers whose software they use, then probably developers would have a more comfortable lifestyle, and project development would become more professional and better organised.
Also, software is different from a web service. If a developer abandons a Free Software project, the code is still out their for somebody else to build on, or perhaps the original developer will return to it after taking a break.
To fight spam we should hold the following responsible: 1) ISP's for not properly configurating their network to block certain traffic to certain home computers ports. Even more so when suspect traffic is noticed. Example, my ISP does not allow outbound port 25 connections. 2) Software companies who develop broken code allowing such activities (IE, Microsoft). Nuff said.
[%] Cingular Ringtones
I'd like to take advantage of the RBL lookups against my own database. Is there any open source software that can accept a DNS lookup message, enable me to lookup the IP in MySQL (for instance), and respond back with a 127.0.0.1 or not?
This would enable me to build my own blacklist from spams coming in to my server for accounts which have NEVER existed, or have only existed on remove lists.
By giving people one entire day to remove their mailer configuration, they didn't leave people much time. Of course, that's sort of moot, I noticed early last week that my mailer wasn't getting responses from them any more, causing timeout delays on the query for every incoming message.
Ah, well. I guess I shouldn't complain, since this one inconsiderate act is vastly overshadowed by the usefulness they've provided over the years.
Oh, you're not stuck, you're just unable to let go of the onion rings.
I remember setting up a filter that would run an open relay check before accepting the mail.
That's when I realized that 99.9% of spam came from Windows zombie boxes, not from mail relays at all.
For adding a few points in SpamAssassin. Other than that, don't rely on it.
I removed my server from checking them today. For grins, I went back a week to see how many uce's they blocked. I did not find one.
Anyone else notice this?
How did I come to find out that we had an open relay? Did ORDB notify us? Hell no. They just slapped us on their list, and our users started getting bounce messages from other mail servers. I fixed the problem quite easily once I knew about it, but the biggest problem was getting off the list!!! That was a whole other nightmare take took longer than hearing about the problem and fixing it.
So I say good riddance. Those guys are pretty bright and meant well, but my experience with them left me with a very bad impression. Hopefully they were more professional in recent years, but from the way they're ending their service, it sure as hell doesn't seem like it.
1. SORBS sucks... and they work because they suck. They assume any mail source is a spam source unless it got a rDNS record (wich may be quite hard to get on ADSL lines). /.).
...whoever find a working non-STASI-like (ie. SORBS) and open solution will get my vote for the Nobel Prize...
...and yes I do know about several methods for fighting spam but they are far from perfect... they are usually based on certificates and they do work pretty well... we do however need a solution in the SMTP and not an propriatary addon on top of it...
2. SpamHaus do a decent job and they don't make funny/crazy assumptions, and they do try to keep the list up to date.
3. Even content check does not block spam... spammers are sending pictures with their message... and they make those hard to run thru OCR (just like the Human-Check here on
4. A world wide law against spam would help but is not likely to happen.
Greylisting? Pfft, purplelisting is where it's at.
ORDB always attempted to notify the administrators of listed servers, several variations on the postmaster@server would have been sent and ignored by the people maintaining the server before you.
-- Andreas
The zone has been emptied, so nothing will break due to the shutdown of ORDB.
-- Andreas
So long, and thanks for all the phish?
Perhaps you are asking about SPF.
o rk Spammers recently started forging my domain as their return address. I know this because I recieved a bucket-load of bounces every day until I blocked the catch-all address. All of that spam would have been blocked if the servers that bounced it had checked my SPF record first. It clearly specifies that all of the IP addresses where the spam is coming from are not authorized to serve email from my domain.
http://en.wikipedia.org/wiki/Sender_Policy_Framew
This is a simple, open standard that can eliminate spam from forged domains, which I would guess is most of it, at this point in history.
I live in the Phoenix, Arizona, USA area. One morning we all woke up to find the Krispy Kreme donut shops all closed. Articles in the paper described employees showing up to work with the doors chained shut. They were not even told it would happen.
One day about 10 years ago I went to work to find an email response from a significant software component supplier. I had submitted a critical bug report the day before. The response was a canned email saying "Sorry, we are out of business as of four days ago." The company had a muli-thousand dollar licence and support contract with them. Could we sue based on failure to fullfill the contract? Yes, but when they are in recievership, what good does it do to waste time suing?
My point is that commercial projects are not immune to suddenly "going away" and lumping community projects into a pile of unreliable resources is just as valid as saying commercial projects will always be dependable.
This morning in response to "who is going to pay for this Shiieeeet?" 10,000 businesses pointed at "the other guy" and went back to sleep.
That said, I'd been considering removing ORDB from our checks for some time. On days when NJABL and SpamHaus were picking up 30-50k messages each, ORDB would pick up between one and five messages. So, although it's sad to see their passing, for me at least they weren't that important a part of my spam-minimisation strategy.
Gosh, they gave us TWO weekends!
Err... the takedown notice is dated 18 Dec 2006... the takedown date is 18 Dec 2006.
That's 24 hours notice.
Parent needs to get a life.
The satire in question was written by anti-spam advocates; in part to ridicule amateur, armchair philosophers; who think that their knee-jerk response is better than anything the experts have come up over the years.
OTOH first time I saw
(x) Killing them that way is not slow and painful enough
used. Kudos
Crap. What did the new CSS do with the "Post anonymously" option??
I wholeheartedly agree.
SPF certainly cannot stop botnets. It's trivial to setup dummy domains with SPF records that allow sending from your botnet, and it's very cheap to register new domains everyday if you use stolen cerdit card info.
g +hosting-to spammers. I've made several complaints to several ISPs about PCs in their IP range sending out spam from domestic broadband connection, together with contact info (cellphone+promotional websites) of the spammer that sent the spam through their system, and the spammer is still free and continues to send spam that arrives from hundreds of PCs all around the world to my spamtraps. Only the ISPs can have positive evidence about PCs on their network being abused by spammers. I can only point out that one spammer sends email from residential IP spaces of many ISPs all around the world. The ISPs can monitor the known IP addresses (the ones I report to them) and provide law enforcement with positive evidence that the PC have been hijacked and how it is being used without the owner's permission. Apparently they have no interest in doing so. Spammers are selling their services openly and nobody wants to stop they. I asked a spammer for a quote and he got back to me from his ISP email address with a quote that included his street address and phone. It was a spammer that sent mail using botnet (as it seems from the "Received" headers on the spam I received that included the spammer's initial contact address). They're pretty sure nothing will happen for them, and they are making huge progress in selling their spamming services to "legit" businesses.
Botnets could be stopped if ISPs would have wanted to stop them, but then it's more profitable for ISPs to sell anti-spam+anti-virus+anti-spyware+contentfilterin
Spammers rely on you not getting back to them if you don't want what they sell. They send to millions but can only handle so many hundred responses. They are successful because we help them by not replying. Only those that are actually interested in doing business with them contact them.
If a small percetage of those that are not interested call back and express interest (that would not result in a purchase) their business concept collapses.
So go back to the spammers, fill their contact forms with bogus information. Order their stuff with fake CC numbers and fake contact info. Just spam them. Drown them in info they don't need! Make them call back thousands of phone numbers to find out the few who really wanted them to call back!
Their have been attempts to get back at spammers. These have mostly been automated systems that spammers could learn to circumvent or attack back. To really hurt spammers they need to be drowned in real responses from real people that are undistinguishable from real customers.
It can be effective with some sorts of spam, not all (such as not with the spam that encourages buying certain stocks) but it is important to make this particular spam fail, and leave spam to only illegitimate purposes that don't need you to contact them.
I have been feeding some spammers' contact forms with fake phone numbers *actually real phone numbers that I collected from other spammers contact info, why not have them phone each otehr...) It seems to have some effect, as they seem to have added now more rigourous checks on their forms (easily avoided using javascript:document.forms[0].submit()).