Martin Geisler Online

I’m still getting tons of spam sent to my address(es) at GimpsterDotCom, but none of it gets through thanks to the extremely accurate POPFile filter that I use.

POPFile is using good oldfashioned statistics to sort my mail into different buckets — you’re not limited to a simple spam/non-spam classification, POPFile can sort mail into any number of buckets.

I’ve now had 19,275 mails sent through POPFile, and I’ve had to correct it 16 times. This gives an accuracy of 99.92%(!). And what is more extreme, is that it tells me that I’ve received an average of 292 mails each day in the last two months…

Now for the stupid spam that just caught my eye, here’s the headers:

Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: (qmail 20512 invoked by uid 506); 4 Nov 2003 05:42:30 -0000
Received: from [email protected]
by sky.netsite.dk by uid 503 with qmail-scanner-1.20rc1
(clamuko: 0.60. Clear:RC:0:.
Processed in 0.06725 secs); 04 Nov 2003 05:42:30 -0000
X-Qmail-Scanner-Mail-From: [email protected] via sky.netsite.dk
X-Qmail-Scanner: 1.20rc1 (Clear:RC:0:. Processed in 0.06725 secs)
Received: from 216-187-212-197.ded.btitelecom.net (HELO exchange.jano.net) (216.187.212.197)
by mail.netsite.dk with SMTP; 4 Nov 2003 05:42:30 -0000
Received: from smtp0281.mail.yahoo.com ([211.158.48.239])
by exchange.jano.net with Microsoft SMTPSVC(5.0.2195.6713);
Mon, 3 Nov 2003 15:59:29 -0500
Date: Mon, 3 Nov 2003 20:56:38 GMT
From: “wilda “<[email protected]>
X-Priority: 3
To: [email protected]
Subject: $RANDOMIZE

Apparently they spammers cannot even get their filthy software to work correctly… That’s all for now, see ya!

As you’ve all undoubtfully noticed, then I haven’t updated GimpsterDotCom for little over a month now — I’ve simply been doing other things.

I have for example been working on our DAIMI:dOvs project with Lars Petersen and Thomas Mølhave. We’re asked to write a compiler in ML which will be used to compile a subset of Scheme called DAIMI-Scheme into a bytecode format.

The bytecode will be executed by a virtual machine, written in C. We’ve done with most of the VM, except for the garbage collector, and we’ve (well actually Lars Petersen has) just begun to look at writing the compiler.