Need someone to lead product management at your software company? I create software for people that create software and I'm looking for my next opportunity. Check out my resume and get in touch.

Is this the end?

Freshness Warning
This blog post is over 21 years old. It's possible that the information you read below isn't current and the links no longer work.

For months, I’ve laughed in the face of spam. I’ve bared my email address in public, daring the spammers to come and find me. "Let the spam flow," I cried, for I was prepared. I had SpamAssassin on my side.

In the last 5 months, SpamAssassin has caught over 60MB of spam wih nary a false positive or spam slipping through. But now chinks have appeared in my armor. In the last half-hour, four spams have slipped through. Each one was scored just under the five points required in order for a message to be tagged as spam.

Johan Svensson
January 23, 2003 4:44 AM

Personally, I run SpamProbe (spamprobe.sf.net), that uses bayesian logic. For all the recent hype about the Bayes formula, it's damn good. Unfortunately (heh) I don't get any spam at all to my domain, so I had to import a bunch of hotmail spam to train the filter. Sure, after about 300 messages from hotmail, it picked up every piece of spam originating from my hotmail account and nuked it. Though of course, many spams there tend to be repeated messages. Paul Graham's latest paper sounds promising, and adds a new layer to the previously completely naive filter; his suggestion is to differ between different headers, the body and URLs in the message. Personally, I think a system based on bayesian logic is the way to go. It's not the Be All, End All of spam preventing, but it's so incredibly effective that it's a bad idea not to have it among your filters. I've noticed that some of the hotmail spam I've gotten recently have changed style -- it's a short sentence with non-spammy words followed by a URL. That's certainly not much for SpamAssassin to chew on.

Adam Kalsey
January 24, 2003 12:39 PM

The latest SpamAssassin (2.5) has Bayesian filtering built in. I'm still running 2.43, though, because I wnat to make sure that the new release is stable before updating my servers.

andersja
January 24, 2003 3:15 PM

... it's the classig problem of filtering systems with feedback mechanisms... It seems the only way to keep up is to install new versions of SA before the spammers do... Despite the odd slip-through, I couldn't imagine living without it... It catches 1000+ messages for me a month... There are commercial products available that I can't imagine being nearly as thorough as SA and bing sold for massive sums... See also: http://www.jacobsen.no/anders/blog/archives/2002/08/23/is_spamassassin_helping_the_spammers_too_much.html http://www.jacobsen.no/anders/blog/archives/2002/08/28/to_filter_or_not_to_filter.html http://www.jacobsen.no/anders/blog/archives/2002/10/16/spam_hype_and_spamassassin.html

Johan Svensson
January 24, 2003 5:51 PM

It's not that I don't like spamassassin - I used it before switching to spamprobe. It's just that spamassassin is a bit resource hungry and takes longer time due to hostname lookups and such. That's stuff I can live without -- spamprobe includes the headers and server names when analyzing the mail anyway. though of course, I used to run spamassassin on an old Cyrix 100MHz laptop with a whopping 16 megs of RAM. :-)

This discussion has been closed.

Recently Written

Mastery doesn’t come from perfect planning (Dec 21)
In a ceramics class, one group focused on a single perfect dish, while another made many with no quality focus. The result? A lesson in the value of practice over perfection.
The Dark Side of Input Metrics (Nov 27)
Using input metrics in the wrong way can cause unexpected behaviors, stifled creativity, and micromanagement.
Reframe How You Think About Users of your Internal Platform (Nov 13)
Changing from "Customers" to "Partners" will give you a better perspective on internal product development.
Measuring Feature success (Oct 17)
You're building features to solve problems. If you don't know what success looks like, how did you decide on that feature at all?
How I use OKRs (Oct 13)
A description of how I use OKRs to guide a team, written so I can send to future teams.
Build the whole product (Oct 6)
Your code is only part of the product
Input metrics lead to outcomes (Sep 1)
An easy to understand example of using input metrics to track progress toward an outcome.
Lagging Outcomes (Aug 22)
Long-term things often end up off a team's goals because they can't see how to define measurable outcomes for them. Here's how to solve that.

Older...

What I'm Reading

Contact

Adam Kalsey

+1 916 600 2497

Resume

Public Key

© 1999-2024 Adam Kalsey.