Slashdot Mirror

darthcamaro writes "The folks at internetnews.com are reporting that the Spam Assassin project has been promoted to a full top level Apache Software Foundation project..the project has been in incubation for a while and it's finally made it through...the article also reveals that Apache is now using Spam Assassin themselves: 'I think spam filtering is now a critical part of the network infrastructure and Spam Assassin is a leader in the area,' said Daniel Quinlan, chairman of the Apache Spam Assassin Project Management Committee."

Simon Lyall writes "A new study of antispam software shows that Spamassassin performed well in various configurations along with Spamprobe , Bogofilter and Spambayes also came out good while CRM-114 failed to live up to its previous claims . The study shows: 'The best-performing filters reduced the volume of incoming spam from about 150 messages per day to about 2 messages per day.'"

ErrorBase writes "In this Infoworld article, Logan G. Harbaugh makes a great deal about an ancient (2.44) version of SpamAssassin comparing it with newer comercial variants. Quote : You get what you pay for. [...] However, it took more than 10 times as long to install and configure SpamAssassin as it did any of the other products. " Why did he not ask Kevin Railsback who had the whole thing working some while ago?)"

Spamhunter asksL "Everyone has their favorite tools to stop spam at the inbox, whether it's using a scoring tool like SpamAssassin, bayesian filters, or something as extreme as challenge/response whitelists (which creates a few problems itself). What I'd like to know is, what are your tools for actively investigating and shutting down spammers? I've found information sites like SPEWS and Spamhaus to be invaluable in tracking down spam gangs and spam-friendly ISP's in order to put pressure where it belongs. Sometimes just chasing the chain of ownership in WHOIS is helpful. What tools, approaches, and resources do you find helpful?"

Roadmaster asks: "Usually, the most effective spam filtering techniques are somewhat resource intensive. Heuristic checkers like Spamassassin, or bayesian filters like spamprobe are processor and storage hungry. This is fine for small setups; I've been using spamprobe to filter spam for 3 users with great results. I'm now however faced with a big challenge: a mail server that will eventually be handling mail for over 50,000 users and needs to have some sort of anti-spam measures. What are some good and computationally cheap spam prevention measures?"

"Ideally, I'd prefer something that does reject the message if it's spam (SMTP result code 550 or something like that), unlike current Spamassassin or spamprobe setups that accept the message and only later decide whether it's spam. Solutions like MAPS RBL, ORBS are acceptable altough commentary on their accuracy would be welcome. Other possibilities I've thought of include checksumming (Vipul's razor or DCC) and simple header checks that could be implemented for instance in a sendmail milter.

Are several quick checks (DCC + RBL) accurate enough and still cheaper than one slow check (Spamassassin, bayesian filtering)? does stacking of similar techniques improve accuracy significantly? (DCC + Razor, RBL + ORBS). How can the good but expensive techniques be made cheaper? (Spamassassin's spamproxyd, hashed wordlists for bayesian filters, and so on). Discussion on all these aspects would yield some interesting conclusions on quick and efficient spam filtering."

Remember the company who started using haiku to fight spam? According to a news.com article, it will now be tested in court. Habeas is suing two internet marketers, saying that they've included Habeas' haiku in their mail, thereby lowering their SpamAssassin score by 6 points, but allegedly violating the trademark. It's interesting because the end effect of this will be more or less spam, but it's based on trademark law. It'll also be interesting to see how well this holds up across national boundaries.

Duncan Findlay writes "Network Associates Inc. has just acquired Deersoft, Inc., which is known by many as the creator of SpamAssassin Pro, the proprietary (Windows) version of the GPL/PAL licensed SpamAssassin (Mirrors: Eastern US, Europe). It seems that we may see parts of SpamAssassin under the McAfee name within 6 months. You can also read the story at Yahoo or at Reuters. Unfortunately, the SpamAssassin trademark was owned by Deersoft, so hypothetically, NAI could force us to call the Open Source project something else!"

Duncan Findlay writes "Network Associates Inc. has just acquired Deersoft, Inc., which is known by many as the creator of SpamAssassin Pro, the proprietary (Windows) version of the GPL/PAL licensed SpamAssassin (Mirrors: Eastern US, Europe). It seems that we may see parts of SpamAssassin under the McAfee name within 6 months. You can also read the story at Yahoo or at Reuters. Unfortunately, the SpamAssassin trademark was owned by Deersoft, so hypothetically, NAI could force us to call the Open Source project something else!"

Duncan Findlay writes "Network Associates Inc. has just acquired Deersoft, Inc., which is known by many as the creator of SpamAssassin Pro, the proprietary (Windows) version of the GPL/PAL licensed SpamAssassin (Mirrors: Eastern US, Europe). It seems that we may see parts of SpamAssassin under the McAfee name within 6 months. You can also read the story at Yahoo or at Reuters. Unfortunately, the SpamAssassin trademark was owned by Deersoft, so hypothetically, NAI could force us to call the Open Source project something else!"

Duncan Findlay writes "Network Associates Inc. has just acquired Deersoft, Inc., which is known by many as the creator of SpamAssassin Pro, the proprietary (Windows) version of the GPL/PAL licensed SpamAssassin (Mirrors: Eastern US, Europe). It seems that we may see parts of SpamAssassin under the McAfee name within 6 months. You can also read the story at Yahoo or at Reuters. Unfortunately, the SpamAssassin trademark was owned by Deersoft, so hypothetically, NAI could force us to call the Open Source project something else!"

Gothmolly asks: "After reading the recent spate of spam and anti-spam articles here on Slashdot, I decided to beef up the anti-spam security on my own domain. I run my own domain and mail server, running Qmail, along with rblsmptd. Mail that passes this gets hit with Spamassassin However, one particular spamhaus, Clickformail has particularly nasty servers, they try at least 2 SMTP connects/second, and I suspect that's only limited by my 384k DSL pipe. The impact on my box was non-zero, to say the least. I ended up putting a packet filter on their class C netblock to stop the barrage of log messages and increase in load (from 0.05 normal to 0.15). Has anyone else experienced such determined spammers, and what is the best way around it?"

Burl Ives writes "See this CNN Article. 'The FTC encourages consumers to forward any spam they receive to the e-mail address uce@ftc.gov'. I'd say if they've posted their e-mail on the web, they are probably getting as much as the rest of us already, which isn't to say I'm not hoping to see some discussion of using the statistical spam sorters to auto forward a lot to them in encouragement..." I've been using SpamAssassin for some time now with excellent results. Perhaps now I need to have my spam folder auto-forward to the FTC as well.

UCRowerG writes "From CNET News on Yahoo!: "Conceived by Napster co-founder Jordan Ritter and open-source developer Vipul Ved Prakash, the company is touting the benefits of democracy, networking and collaboration in the war against unscrupulous e-mail marketers." " Since Prakesh is responsible for Razor, hopefully there will be Linux support as well, but once again I gotta throw my props at Spamassassin which catches over a hundred spam for me each day.