Re: error writing to filter (bogofilter)

[ keeping you guys up to speed ]

See also:
http://www.bogofilter.org/pipermail/bogofilter/2013-June/009951.html
ff.

* Sam Varshavchik on Saturday, June 15, 2013 at 11:25:31 -0400
> Dimitri Maziuk writes:
>> On 2013-06-14 17:51, Sam Varshavchik wrote:
>>> You should look at what bogofilter is printing, for the offending
>>> messages. It can't be the original message, if bogofilter isn't even
>>> reading it. Perhaps looking at bogofilter's output, for the message,
>>> will provide more clues.

~$ 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

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

>> Well, in theory bogofilter could drop the pipe before reading the last
>> \n so its output would look fine...
> 
> bogofilter has no way of knowing it's the last \n until it reads
> everything, and gets an EOF.
> 
> However, if the purpose of the -p option, as documented, would be to
> read the entire message, do whatever bogofilter wants to do with it,
> which seems to be just add some headers to it, and write it out, then
> it's reasonable to expect that this is what it should do.

It seems to concern multipart only, and I'm starting to wonder
whether some temp file writing problem is involved.

-- 
\black\trash movie   _SAME  TIME  SAME  PLACE_
	       New York, in the summer of 2001

--->> http://www.blacktrash.org/underdogma/stsp.php

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev