netflap.com Blog

I am a big fan of the linux operating system because (like I’ve said before) it creates competition in a market which is in dire need.  As powerful as Linux may be, it doesn’t mean that it is ready for every home user in the world to switch to tomorrow.

In order for an operating system to be used by “the public”, it has to be relatively simple.  If they want something, they should have to click, answer a few questions and move on.  This is what Windows provides and this is what will be required of Linux before it is able to start taking significant market share.

Now, this won’t be a long ranting post, but what I do want to say is that Linux is almost ready.  I recently setup a drive array (software RAID 5) in Linux and found that with the most recent version of the Kernel, it was able to detect all of my hardware and required very little “hacking” to get working.  In my opinion hardware detection was the previous downfall of Linux, however from my recent experience, this problem is well on its way to being fixed.  More vendors are releasing Linux drivers and more legacy drivers for older hardware are being released all the time.  As the userbase grows, so will the support.

I now have a spare computer which I can use as my Linux desktop test.  I’m going to see how much of my day to day computer work I could do using a Linux desktop and what problems I run into.  I’ll be recording my experiences here.

TrackBack to 'Linux is almost ready'.

A lego rubber-band chaingun which fires at 11 rounds/second.  I really don’t think there is much else to say.  For those who need to hear more, don’t bother, and for those who understand the cool factor here, check out the details here.  I have to say, that is some mighty fine Lego work.  Be sure to check-out the video that goes along with it.

Also, I’m heading out on vaction tomorrow, I’ll be going to California and will be stopping by Legoland.  I’ve never been before, so I’m hoping they will have some additions for my new Mindstorms NXT set.  I’m going to need more supplies if I’m going to make a better device than the chaingun.

TrackBack to 'Lego chaingun – Need I say more?'.

I seem to be writing a lot of rants lately, but hey, that’s just how it goes.  Another question I have about users is why is it that whenever something goes wrong with a computer, it’s the computer’s fault.  People have the impression that computers are there to do things for them, when really, a computer is just a tool.  A computer helps a person with mundane tasks to accomplish a goal

The underlying problem here is that the big software companies (you know who) have tried to make the computer a friendly device which acts more like a co-worker than a typewriter.  People treat the computer like another person because it asks them questions and cute little paper-clips talk to them.  The function of asking questions and talking to them is simply a method of extracting information from people who can’t tell the computer what they want.  But from the user’s point of view, the computer is talking to them and therefore is doing things for them.  This is where things break down.

You see, so the user ends up thinking the computer is doing something for them when really they are using the computer to do something for themselves.  So when something goes wrong, it’s the computer’s fault, because the computer was doing it.

Now there are some cases where software or hardware is defective and in those cases, yes, the computer is to blame.  But when someone is using a program that is known to crash often, and they still continue to use it… can they really blame it when they lose their file?

TrackBack to 'It’s the computer’s fault'.

SPAMassassin has become an extremely efficient SPAM filtering solution and is currently the most accurrate way to eliminate the majority of SPAM coming into a corporate network.  The problem is that you can configure SPAMassassin in MANY ways and depending on how it is done, you can go from filtering 75% of the SPAM to filtering 99.9% of the SPAM.  I’ve configured a fair number of SPAMassassin installations in my time for a wide variety of organizations and here are my tips for getting closer to 99.9% accuracy.

1. Keep up to date
The best tip I can give you to have better results is to use the latest version of SPAMassassin.  You don’t need to have bleeding edge, but just make sure you aren’t using a version which is a year or two old.  Update your installation every few months if you can.  The newer versions of SPAMassassin are always adding new detection techniques and rules which help cut out a vast majority of SPAM.  I’ve found that newer features such as the URIBL are able to cut your false negatives down by 80%.

2. Use a third party ruleset.
The SPAMers find ways around the base rules in SPAMassassin all the time, so the more rules you can add, the better (as long as they are good rules).  SARE is a great resource for a constantly updated set of third party rules.  These rules are all tested and help to greatly increase the accuracy of your filter.  A script called RulesDuJour is also available which automatically downloads these rules for you and updates your installation with the latest ruleset at a scheduled time every day.  Having a constantly changing ruleset makes it difficult for the SPAMers to get around the filter.

3. Train your Bayes engine
SPAMassassin comes with a bayesian learning engine which allows it to use statistical methods to categorize a message a SPAM or HAM (not SPAM).  This engine is extremely accurate as long as it has the proper training.  In order to train the bayes engine you need to provide it with messages that have been reviewed by a human and are confirmed to be either SPAM or HAM.  You can manually train the engine using the sa-learn command, however it is far more efficient to use a front end to SPAMassassin like Maia Mailguard.  With Maia, it keeps a copy of all messages that pass through it so that if a message either gets filtered when it shouldn’t have or doesn’t get filtered when it should have, you can go back and mark the message as either SPAM or HAM.  This will then train the Bayes engine and it will then filter similar messages in the future.  I’ve really just touched on the Bayes engine in SPAMassassin and therefore you should look it up online and read more about it to find out what the best method would be for your environment.

4. Use the SPAM network detection methods
There are several blacklists and hash detection methods that can be used in SPAMassassin.  The two that I highly recommend are DCC and Razor.  These two products will help to increase the accuracy of your SPAM filter again by a large percentage.  Support for the products is builtin to SPAMassassin by default but they do require a client to be installed in order for them to start working.  A quick search online will provide many tutorials for getting them going.

Those are the big four tips I have.  There is a lot of other tuning you can do, but by making sure you are doing the above four things, your accuracy should easily be above 98%.  Using this configuration, I am currently seeing about 99.4% accuracy for detecting SPAM and only about 0.01% false positives.  If you have any other good tips for SPAMassassin, please leave a comment.

TrackBack to 'Increasing SPAMassassin’s accuracy (4 tips)'.