Well, it happened

[Dan Stromberg]

Sick of base64 spam, I decided to upgrade my bogofilter.

And it's a mess.

My procmail filters are broken (I'm getting more spam than ever), and my
evolution support is broken (I can't mark a message as spam anymore).  I
haven't looked at my mutt support yet, but it's probably broken too.

How might these procmail rules need to be changed for the new semantics?

:0HB
* ? /dcs/packages/bogofilter/bin/bogofilter
{
   :0c
   | /dcs/packages/bogofilter/bin/bogofilter -s

   :0
   $MAILDIR/bogofilter
}

:0EHBc
| /dcs/packages/bogofilter/bin/bogofilter -n


My evolution filters use bogofilter -S -l, bogofilter -N and bogofilter
-u.  How much of this should I expect to need to change?

-- 
Dan Stromberg DCS/NACS/UCI <strombrg at dcs.nac.uci.edu>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://www.bogofilter.org/pipermail/bogofilter/attachments/20030313/24a403e8/attachment.sig>