Actually, I like the ability to interface with external programs for mail filtering/processing. My main reason for preferring this is that it allows each group of developers to continue doing what they do best. Another benefit is that if a better algorithm than Bayesian comes along, it will be a simple matter to "bolt on" that implementation.
On a side note, I *would* like to see evolution support filtering based on its contact lists. This is a fairly old request, but worth doing. My understanding of the reason that it's not been done yet is that the contact manager part of the application is not thread safe, and can't easily be combined with the mail part (which uses threads).
I really hope that they can resolve the issue and implement it eventually. Not only would you be able to set up white- and black- lists, but you could also direct incoming mail to various folders based on contact categories. This has real value, and I'd much rather see the Ximian developers focus on it than on implementing Bayesian algorithms that are already usable through the pipe to shell interface.
2. Make a shell wrapper script that runs bogofilter in passthrough mode, redirect stdout and stderr to files in/tmp for debugging and training bogofilter. Here's mine:
3. Make a new local mail folder in evolution to collect spam.
4. Make a filter in evolution that runs the wrapper script. Tools->Filters, choose Incoming, choose Add. Add a criterion that looks like this: Pipe message to shell command, (path to your wrapper script), returns, 0. Add an action to move the message to your local spam filter.
5. Be sure evolution is set to apply filters to new mail in the inbox(es) you want bogofilter to act on. Tools->Settings, choose Mail Accounts, choose desired inbox(es), choose edit, choose the Receiving Options tab, check the Apply filters to new messages in INBOX on this server.
Please be sure to RTF bogofilter M. You will need to train (and retrain) bogofilter with spam and non-spam samples over time. The switches to do this have CHANGED from version to version. If you have set things up as above, you can use/tmp/bogo.out to retrain bogofilter for the last message processed when necessary.
Slashdot Mirror
Ooops, corrections!
/usr/bin/bogofilter -p -u > /tmp/bogo.out 2> /tmp/bogo.err
In step 2, the first 2 lines of the shell script lost the newline between them. They should be:
#!/bin/bash
In step 4, the last sentence should end with "...local spam FOLDER" (the one you created in step 3).
Actually, I like the ability to interface with external programs for mail filtering/processing. My main reason for preferring this is that it allows each group of developers to continue doing what they do best. Another benefit is that if a better algorithm than Bayesian comes along, it will be a simple matter to "bolt on" that implementation.
On a side note, I *would* like to see evolution support filtering based on its contact lists. This is a fairly old request, but worth doing. My understanding of the reason that it's not been done yet is that the contact manager part of the application is not thread safe, and can't easily be combined with the mail part (which uses threads).
I really hope that they can resolve the issue and implement it eventually. Not only would you be able to set up white- and black- lists, but you could also direct incoming mail to various folders based on contact categories. This has real value, and I'd much rather see the Ximian developers focus on it than on implementing Bayesian algorithms that are already usable through the pipe to shell interface.
Yes, I've done it and here's how:
/tmp for debugging and training bogofilter. Here's mine:
/usr/bin/bogofilter -p -u > /tmp/bogo.out 2> /tmp/bogo.err
/tmp/bogo.out to retrain bogofilter for the last message processed when necessary.
1. Get and install bogofilter.
2. Make a shell wrapper script that runs bogofilter in passthrough mode, redirect stdout and stderr to files in
#!/bin/bash
status=$?
exit $status
3. Make a new local mail folder in evolution to collect spam.
4. Make a filter in evolution that runs the wrapper script. Tools->Filters, choose Incoming, choose Add. Add a criterion that looks like this:
Pipe message to shell command, (path to your wrapper script), returns, 0. Add an action to move the message to your local spam filter.
5. Be sure evolution is set to apply filters to new mail in the inbox(es) you want bogofilter to act on. Tools->Settings, choose Mail Accounts, choose desired inbox(es), choose edit, choose the Receiving Options tab, check the Apply filters to new messages in INBOX on this server.
Please be sure to RTF bogofilter M. You will need to train (and retrain) bogofilter with spam and non-spam samples over time. The switches to do this have CHANGED from version to version. If you have set things up as above, you can use
Good luck, and happy spam filtering!