Bastard Operator From Hell
Any BOFHs out there recognizing themselves? 🙂
(Yes, I know, this is not the original BOFH, but this guy is acting like a BOFH.)
Archive for year: 2010
All icons on the desktop has Microsoft Internet Explorer icon
There is a practical joke being spread to Windows Vista users trying to fool them to associate .lnk (shortcuts) files with Microsoft Internet Explorer (MS IE). The so called joke in this is that it is very easy to do, but almost impossble to undo of you are not a skilled computer technician. This is because there is no possibility for the user to “unassociate” a file extension once it has been associated.
FreeBSD 6.3 end-of-life January 31, 2010
Conservative users can upgrade to FreeBSD 6.4-Release (EoL November 30, 2010) or FreeBSD 7.1 (EoL January 31, 2011) which both are extended life releases. Others should upgrade to FreeBSD 7.2-Release or 8.0-Release.
For more information, see FreeBSD.org.
New year – and a little year 2010 bug
The 200x ended and we went into 2010. So we got ourselves a little 2010 bug. It was in the spam filtering software Spamassassin. Or to be more precise in it’s rulesets.
The problem was actually discovered and fixed months ago but someone forgot to include it in the rulesets for Spamassassin 3.2.x. No hard feelings about that. Those guys are doing a great job and shit do happen. It was fixed in a couple of hours on January 1, 2010.
The problem was that all incoming mail filtered by Spamassassin was flagged with FH_PAST_DATE_20XX and given an extra +3.4 spam score which results in false positives.
Those that were running sa-update by cron had this automatically fixed as the updated rules were on the servers around noon on January 1, 2010. Those not running sa-update by cron… still have problems unless they have run sa-update manually. Saying that, running sa-update by cron might be a good idea to keep your Spamassassin rules updated 🙂 A script for doing so and getting a mail with the result can be found here.
Some FreeBSD users reported that sa-update was not able to pull down the updated rules. A manual workaround and links to details around the problem is found here.