Re: procmail: Non-zero exitcode (1) from "/usr/bin/bogofilter"

On Mon, 17 Sep 2007 06:47:25 -0400
[email protected] wrote:

...[snip]...
> > "-N -s" is appropriate when the message was (1) incorrectly entered
> > into the wordlist as ham, i.e. using "-n", (2) should have been
> > entered as "spam", and (3) you're correcting the situation.
> >
> > Most often "-Ns" is used when the "-u" (auto-update option) is part
> > of the default running of bogofilter.  With auto-update, "-Ns" is
> > used for fixing a false negative (spam incorrectly classified as
> > ham).
> >
> > If a message has _not_ been registered as ham, then using "-N' is
> > WRONG.  Using "-Ns" frequently (and incorrectly) could result in the
> > ham count being forced down to zero (which is a very BAD thing).
> >
> > HTH,
> >
> > David
> >
> Which is exactly what has happened in my case.  So that being said,
> I need to change my script, perhaps using just bogofilter -sv  
> </var/local/imp-spam (imp-spam is a mbox) instead of Ns.  But the  
> emails that get reported as spam are incorrectly labeled as ham, and  
> in most cases there are quite a few of the same emails that are in
> the imp-spam mailbox.
> 
> thanks,
> ddh

Hi Dwayne,

"-N" and "-S" are for correcting errors made in _registration_, i.e. if
a message has been fed into the wordlist as ham (with "-n") but is
really spam and is now being fed in as spam, then "-Ns" is needed (to
undo the "-n" and then do a "-s").  As I understand your setup the "as
ham" part isn't being done so there's no need for the "undo" part.

HTH,

David
_______________________________________________
Bogofilter mailing list
[email protected]
http://www.bogofilter.org/mailman/listinfo/bogofilter