[was: problems upon upgrade]

David Relson relson at
Thu Jul 29 07:43:51 EDT 2004

On Wed, 28 Jul 2004 20:25:42 -0800
jerry wrote:

> On Wednesday 28 July 2004 07:10 pm, David Relson wrote:
> >
> > Are you using procmail or maildrop or something else?  Were you
> > using"bogofilter -p -e" and checking for "X-Bogosity: Yes" or were
> > you checking bogofilter's return codes?
> from my .procmailrc
> :0fw
> | /usr/bin/bogofilter -f -p  -u -l -e -v
> :0H
> * ^X-Bogosity: Spam, tests=bogofilter
> * ? bogofilter
> /dev/null


I see several problems in the snippet above.  First, the "-f" flag is no
longer accepted by bogofilter and causes it to exit.  (Try running your
bogofilter command "/usr/bin/bogofilter -f -p  -u -l -e -v" from the
command line).  Second, the procmail recipe doesn't include any error
recovery, which makes it possible for a bogofilter error to lose mail.
Lastly, the "* ? bogofilter" line runs bogofilter a second time, which I
think is unnecessary.

My procmail recipe is shown below.  It causes procmail to retry in case
of error (which helps prevent lost mail) and it checks the message for a
bogofilter spam indicator -- proof positive that bogofilter _has_
classified the message.


------ Begin /etc/procmail snippet ------

| bogofilter -p -l -e -u
#### begin error catcher ####
# m-a 10/28/02
#     if bogofilter failed, return the mail to the queue, the MTA will
#     retry to deliver it later
#     75 is the value for EX_TEMPFAIL in /usr/include/sysexits.h
#### end error catcher ####
* ^X-Bogosity: (Spam|Yes)

------ end /etc/procmail snippet ------

More information about the Bogofilter mailing list