Bogofilter Behaviour on encountering error is unacceptable.

[Matthias Andree]

K T Ligesh schrieb:
> On Tue, Feb 20, 2007 at 11:50:57PM +0100, Matthias Andree wrote:
>> The default behavior is about as sane as it can get: describe what the
>> user needs to do to fix the situation, and exit with an error code.
>>
>> There is no such thing as a default integration scheme, it's all up to
>> the user what he or she makes of the exit code, and write scripts to
>> deal with such conditions.
>>
>> We're not going to play double paranoid, because that game has no end.
> 
>  Munging the mail when it encounters a configuration error is a bit draconian. For instance, spamc from spamassassin will return the entire mail unaltered when it can't contact spamd service.

I don't care what third-party software that bogofilter doesn't interact
with is doing. If you want spamassassin, use spamassassin.

>  My idea of spam filter is one that will _tag_ the message if it can, and leave the message unaltered when it can't. Isn't that much more logical and simple behaviour?

I got your expectation, but bogofilter isn't doing that and isn't going
to. Use maildrop, procmail, write a .qmail snippet...