HP UX Internet Express Software manual Mutt Integration with Bogofilter

:0:

*^X-Bogosity: Yes, tests=bogofilter spam-bogofilter

Mutt Integration with Bogofilter

The following .muttrc lines will create mutt macros for dispatching mail to bogofilter.

macro index d "<enter command> unset wait_key\n\ <pipe-entry> bogofilter -n\n\ <enter-command>set wait_key\n\ <delete-message>" "delete message as non-spam" macro index \ed "<enter-command> unset wait_key\n\ <pipe-entry> bogofilter -s\n\

<enter-command> set wait_key\n\ <delete-message>" "delete message as spam"

Pine Integration with Bogofilter

Using bogofilter with Pine involves the following setup process.

First, enable the UNIX pipe commands in your Pine configuration file. From Pine's main menu:

1.Enter S (Setup)

2.Enter C (Config)

3.Go to the list under Advanced Command Preferences and use the down-arrow key to highlight enable-unix-pipe-cmd.

4.If necessary, "set" this preference by entering X.

5.Enter E (Exit Setup)

6.Enter Y (Save Changes)

Then, edit your ~/.procmailrc file and add the following lines:

:0fw

bogofilter -u -e -p :0e

{ EXITCODE=75 HOST }

:0:

*^X-Bogosity: Yes, tests=bogofilter mail/incoming.spam

Then, bogofilter still needs to be trained to differentiate spam and non-spam messages.

1.While executing Pine, open your INBOX (or the folder where you save incoming messages) and for each spam message highlight the message in the message index, press the key, and enter bogofilter -s.

2.For each non-spam message: highlight the message in the message index, press the key and enter bogofilter -n.

Mail Transport Agent (MTA) Integration with Bogofilter

Bogofilter can also be integrated into any MTA to filter all incoming mail. While the specific implementation is MTA dependent, the general steps are as follows:

1.Install bogofilter on the mail server.

2.Prime the bogofilter databases with a spam and non-spam corpus. Since bogofilter will be serving a larger community, it is important to prime it with a representative set of messages.

3.Set up the MTA to invoke bogofilter on each message. While this is an MTA specific step, you'll probably need to use the -p, -u, and -e options.

4.Set up a mechanism for users to register spam/non-spam messages, as well as to correct misclassifications. The most generic solution is to set up alias email addresses to which users bounce messages.

130 Mail Delivery Administration