Bogom is a sendmail milter designed to connect with bogofilter, providing a straightforward solution to help safeguard against email spam.
Bogom is a sendmail milter designed to interface bogofilter, a bayesian filter. The bogom plugin is intended to be used with only one words database for the entire system. It can be used with the milter API of sendmail(8) to filter incoming mails according to the spam classification determined by bogofilter(1).
The software offers several options to users. For instance, mail classified as spam can either be rejected with the -R option or discarded with the -D option. The -t option allows the user to train bogofilter with the mail classified as spam/ham. Users can enable verbose logging with the -v option. The -u user is a user to run the milter, defaulting to bogofilter.
Users may also specify other options, such as a path to connect to sendmail, a path to the bogofilter(1) binary, the exclusion string and length limit in bytes to be processed from mail body, a path to the file to store the pid of the milter, and more.
The default policy for bogom is to add the X-Bogosity header and deliver the mail. This can be changed with -R or -D when bogofilter classifies the mail as spam. The bogofilter_dir token should be set to the directory with the system database, usually /var/spool/bogofilter, in bogofilter's configuration file, or simply the words database of the unprivileged user running the milter can be used.
Bogom uses a temporal file to store each individual message and forks a new process to scan it with bogofilter. This temporal file uses /tmp directory by default, it's owned by the user running the milter and has 0600 mode. When a directory is specified in quarantine_mdir, the tmp subdirectory in that maildir is used as temporal directory.
Users should take caution with the -t option, which registers the mail after classifying it as spam or ham. This option can be dangerous because the filter may register errors. Users are advised to read bogofilter's manual regarding this point.
This release of bogom includes minor fixes to improve Linux compilation and Postfix support.
The software offers several options to users. For instance, mail classified as spam can either be rejected with the -R option or discarded with the -D option. The -t option allows the user to train bogofilter with the mail classified as spam/ham. Users can enable verbose logging with the -v option. The -u user is a user to run the milter, defaulting to bogofilter.
Users may also specify other options, such as a path to connect to sendmail, a path to the bogofilter(1) binary, the exclusion string and length limit in bytes to be processed from mail body, a path to the file to store the pid of the milter, and more.
The default policy for bogom is to add the X-Bogosity header and deliver the mail. This can be changed with -R or -D when bogofilter classifies the mail as spam. The bogofilter_dir token should be set to the directory with the system database, usually /var/spool/bogofilter, in bogofilter's configuration file, or simply the words database of the unprivileged user running the milter can be used.
Bogom uses a temporal file to store each individual message and forks a new process to scan it with bogofilter. This temporal file uses /tmp directory by default, it's owned by the user running the milter and has 0600 mode. When a directory is specified in quarantine_mdir, the tmp subdirectory in that maildir is used as temporal directory.
Users should take caution with the -t option, which registers the mail after classifying it as spam or ham. This option can be dangerous because the filter may register errors. Users are advised to read bogofilter's manual regarding this point.
This release of bogom includes minor fixes to improve Linux compilation and Postfix support.
What's New
Version 1.9.2: N/A