1 |
On Fri, 2002-11-08 at 15:22, Alan wrote: |
2 |
> The two limitations of bogofilter that need to be addressed someone are: |
3 |
> 1 can only "interact" with it through mutt or some custom hacking |
4 |
> through other programs (I think that emacs vm can notify |
5 |
> spam/non-spam with bogofilter if you know the right spell) |
6 |
> 2 needs enough spam and non-spam to properly set up the word lists. |
7 |
> |
8 |
> However, if 2 is done right, then 1 isn't a real problem. |
9 |
|
10 |
These are excellent points. I saved lots of stuff from my Yahoo! and |
11 |
Hotmail bulk folder, as well as other spams I got for about a week to |
12 |
train bogofilter. I don't remember how much of my good mail I trained |
13 |
it with, but I have a lot saved. Finally, once I installed it into my |
14 |
mail chain via procmail, I used fetchyahoo to get mail from my Yahoo! |
15 |
account from my inbox and Bulk mail folder, so I could monitor the |
16 |
results for a while. No problems whatsoever. Once I was convinced that |
17 |
the Bulk mail folder stuff wasn't getting into my inbox, I stopped |
18 |
retrieving that. |
19 |
|
20 |
As far as point 2, what I did is to create a folder that I put spam in, |
21 |
if it happens to get through. I then have a cron job that runs the |
22 |
contents of that folder through bogofilter -S (this is not ham, this is |
23 |
spam!). I don't have the folder for fixing false positives, but then |
24 |
again, I haven't had any. |
25 |
|
26 |
If you are interested, here is the script that I run from cron every few |
27 |
hours to clean out my spam folder. Note that there is a locking issue |
28 |
with my rm and touch of the spam file, but I didn't really care: |
29 |
|
30 |
#!/bin/sh |
31 |
|
32 |
$HOME/pub/bin/linux/bogofilter -S < $HOME/mail/Spam |
33 |
/bin/rm -f $HOME/mail/Spam |
34 |
touch $HOME/mail/Spam |
35 |
|
36 |
Chad Huneycutt |
37 |
|
38 |
|
39 |
|
40 |
-- |
41 |
gentoo-dev@g.o mailing list |