maildrop + bogofilter: error writing to filter

[Christian Ebert]

* Matthias Andree on Saturday, June 15, 2013 at 15:29:42 +0200
> Am 15.06.2013 12:44, schrieb Christian Ebert:
>> 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?

Multipart. 

> Particular sizes?

328k.

> Maildrop behaviour differs depending on messages size;
> particularly, it will cache small messages in RAM.

I'm receiving smaller and larger messages w/o problem.

David now should have a copy. Interestingly enough bogofilter
choked also on the tar.bzipped message attachment that I bcc'd to
myself.

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

$ maildrop < testbogomsg
maildrop: error writing to filter.
maildrop: Unable to filter message.

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

~$ cat testbogomsg | bogofilter -u -e -p 1>/dev/null
~$ echo $?
0
~$ cat testbogomsg | bogofilter -u -e -p >| bogoout
~$ diff testbogomsg bogoout
94a95
> X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.3

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

What exactly?

$ uname -a
Darwin krille.blacktrash.org 12.4.0 Darwin Kernel Version 12.4.0: Wed May  1 17:57:12 PDT 2013; root:xnu-2050.24.15~1/RELEASE_X86_64 x86_64
 
> In order to debug this, we'd need to know:
> How exactly does Postfix integrate with maildrop?

$ postconf mailbox_command
mailbox_command = /usr/local/bin/maildrop -d ${USER}

-- 
_BAUSTELLEN_ lesen! --->> http://www.blacktrash.org/baustellen