maildrop + bogofilter: error writing to filter

[Matthias Andree]

Am 15.06.2013 12:44, schrieb Christian Ebert:
> Hi,
> 
> I tried my luck at the courier-maildrop list
> http://sourceforge.net/mailarchive/forum.php?thread_name=20130613110855.GB753%40krille.blacktrash.org&forum_name=courier-maildrop
> but was basically referred to bogofilter. So here goes:
> 
> After an upgrade to Mac OS 10.8.4 (64bit) from 10.5.8 (32bit) I
> get the following error for _some_ messages:
> 
> temporary failure.
> Command output: maildrop: error writing to filter.
> /usr/local/bin/maildrop: Unable to filter message.

What are the message properties?   Particular sizes?  Maildrop behaviour
differs depending on messages size; particularly, it will cache small
messages in RAM.

> The offending rule is rather bog standard:
> xfilter "/usr/local/bin/bogofilter -u -e -p"

Be sure to capture its stderr somewhere you can find it. Perhaps
redirect it to a separate log file.

> Trying the bogofilter suspect on an offending message however
> seems to cause no problems:
> 
> $ bogofilter -u -e -p < testbogomsg 1>/dev/null
> $ echo $?
> 0

As Jonathan mentioned, you are not reproducing the exact environment
maildrop would launch bogofilter in.

This, however, goes beyond what Jonathan wrote: user ids, environment,
and possibly more.

> The problem is that bogofilter works fine from the cli - like
> maildrop does, but not in actual delivery. Right now I have to:
> 
> 1. inspect the postfix queue
> 2. in case there is this problem, disable bogofilter by
>    temporarily changing the mailfilter
> 3. sendmail -q
> 4. reinstate bogofilter in the mailfilter
> 
> Needless to say this cannot even be called a workaround.
> 
> Any ideas?

In order to debug this, we'd need to know:
How exactly does Postfix integrate with maildrop?