OK I'm home now and these are the two relevant settings in your popfile.cfg

port 2110
ui_port 8081

There's nothing else that deviates from the normal configuration in the file

Here's my script:

#!/bin/bash
##################################################
# popstart 15/01/03 rickfrm
# This is a script used to start the popfile server as a
# normal user. I keep it in ~/popfile and put a symlink to
# it in ~/.kde/Autostart with the command:
# "ln -s ~/popfile/popstart ~/.kde/Autostart/popstart"
# you will have to give it a permission set appropriate for
# your user in your distro.
##################################################

cd /home/rick/popfile

perl ./popfile.pl >> /dev/null 2>&1 &

# End of script

As you can see It's named popstart. Well I got the ports right :^)

You could probably cut and past that right out of you browser into a gui editor but as with all scripts, its best to give it one more carriage return after after the line "# End of script"

Follow the directions for doing a sym link to ~/.kde/Autostart as above.

I've been quite pleased with popfile's ability to filter spam. Occasionally spam gets through but the mistake is never made again and it is usually someone/thing very unexpected gets classified as spam when its not.

Since 20/11/03 I have had 10,244 emails classified 106 of which were missclassifications. Roughly 98.96% accuracy. Note that I had been running popfile for awhile before resetting the statistics in Nov last year. You will probably have to wait awhile as it builds up its dbase before you start getting high 90's accuracy.

I tag what I want as [g] and the spam as [spam]. Popfile is set up so that the [g] is not appended to the subject line so that it doesn't show up in replies to lists. There is a filter set up in kmail that sends anything with [spam] in the subject line to the Trash folder and the trash gets emptied whenever I choose or close kmail. As a general rule I check out trash (just in case) before I shut down. I probably could do without the [g] tag but I just never got around to changing the configuration.

I hope that helps

Yeah I used popfile on Windows for ages, It was generally 97-98% accurate, but I ditched it when Thunderbird came out, cause I was using Netscape which had been bugging me for a while. Anyway I use Gnome, any chance you could help me figure out how to do the same thing there?

I dont know anything about gnome and I don't know what mail client you would use but here goes:

Do you have a gnome directory in your user account where configurations for gnome programs reside? If so look for a start up script that starts things up when gnome starts up a user session and sym link your script there (like ~/.kde/Autostart). If not look for a gnome start up script elsewhere. I'm sure there'd be one around somewhere.

Alternatively, sym link the script into /etc/rc.d/rc.local. That'll start your popfile server at boot. To know that popfile is initiating at boot add the line " echo "Starting popfile server" " (remove outside set of quotes) to the the script I posted above and it'll show up as a message to your terminal as slack boots up along with any other servers initiated from /etc/rc.d/

I started using popfile when it was not multi user so I set it up in user accounts. I believe the lastest cross platform version can be multiuser. So starting it at boot would let more than one user have access to it but consider that one persons spam might be another persons treasure.

As for the configuration of a mail client, the settings would be the same but just entered somewhere different.

Assuming you have a POP account, in the place where you would configure your email client's pop account, your settings would change like this:

Port 110 becomes Port 2110

Host was: mail.ispnamet.com.au
Host now is: 127.0.0.1

Login name was: username
Now becomes: mail.ispname.com.au:username

Hey thanx for all your help! I got it going in the end, I added

cd /usr/popfile

perl ./popfile.pl >> /dev/null 2>&1 &

to /etc/rc.d/rc.local and it worked fine after a reboot, I didn't need to change the port numbers or anything, it just works!
It looks like the main difference is that justwantin had ./pop.... whereas we were trying /pop.... (maybe)
Some say Slackware is too hard, but Slackware users are possibly the most helpful people I've come across. So thanx again.