Well, it happened

[David Relson]

At 10:55 AM 3/13/03, Dan Stromberg wrote:

>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?

Hi Dan,

Sorry to hear you're having troubles.

The '-s' and '-n' options have not changed, so the procmail rules should be 
fine.

The '-S' and '-N' options have become "unregister only" so the evolution 
filters will need updating.  "-S" used to mean "move from ham to spam" 
which is now stated as "-Ns" meaning "unregister from ham ('-N')" and 
"register as spam ('-s')".  Similarly "-N" used to bee "move from spam to 
ham" and is nos "-Sn" meaning "unregister from spam ('-S')" and "register 
as ham ('-n')".

So in your evolution filters two option letters will become four, i.e. 
replace -S by -Ns and replace -N by -Sn.  (Note:  option letters can be 
joined or separated, i.e. "-Ns" can equally well be written as "-N -s".

David