upgrading from 0.9.1.2 - and now: working with exim4.22w/exisan

[Matthias Andree]

Karl Schmidt <karl at xtronics.com> writes:

> I have to agree - it just didn't work as well - now it is not working at
> all as I up dated to Exim 4.22 with exiscan to block the virus mess - I
> was getting 2 -3 copis a minut earlier today along with bougus bounce
> messages. (You really would think that most sys admins would have by now
> caught on to the idea that the headers can be forged)
>
> The error codes must have been changed - anyone have exim 4.22 working
> system wide with bogofilter?

Yes, I resisted when the suggestion was made to shift "error" from 2 to
3 and assign the 2 to "unsure", but was overruled.

There is now a fixed-format stdout printout that you request with "-T"
that isn't supposed to change, which may be useful.

Application note: run bogofilter -e -T and capture its stdout, untested example:

#! /bin/sh
EX_TEMPFAIL=75 # take this from /usr/include/sysexits.h
exec <message
result=`bogofilter -e -T` || exit $EX_TEMPFAIL
case $result in
  U*|H*) # was ham
         deliver
         ;;
  S*)    # was spam
         reject
         ;;
  *)     echo >&2 "Unparsable result \"$result\""
         exit $EX_TEMPFAIL
esac

If bogofilter -e exits nonzero, there was trouble.

Short explanation:

       The  -T  provides  an  invariant terse mode for scripts to
       use. bogofilter will print an abbreviated  spamicity  mes­
       sage  containing 1 letter and the score. Spam is indicated
       with "S", ham by "H", and unsure by "U".

       The -e (embed) option tells bogofilter to exit with code 0
       unless there was an error (even if the mail is not spam or
       classified as unsure). This  simplifies  using  bogofilter
       from procmail or maildrop.

-- 
Matthias Andree