Re: error writing to filter (bogofilter)

* Sam Varshavchik on Thursday, June 20, 2013 at 07:01:45 -0400
> Matthias Andree writes:
>> we appear to see that maildrop-on-new-MacOS does not get all data
>> through xfilter.  David Relson traced in- and outputs of bogofilter, and
>> it looks as though the stdin that bogofilter is getting is truncated at
>> exactly 40 kBytes.  Hints as to the problem below.
>> 
>> Is there a way to log more details when writing to the xfilter
>> socketpair or pipe (whatever it's using, I haven't read your code),
>> especially like name, decoded errno, and thereabouts?
>> (I hope I see more in dtruss output.)
> 
> Nope, the loop that writes the message to the pipe does not do any
> logging of its own. If write() returns an error, and it's not EINTR,
> then you get "maildrop: error writing to filter." It's fairly simple.

My layman's summary:

1) Not related to bogofilter, can be replicated with this minimal
config:

xfilter "/bin/cat"
to "$DEFAULT"

2) Happens with any kind of message > 40kb

I suspect an issue regarding temp files and/or with clang and/or
header files, but have C or C++ experience whatsoever.

-- 
theatre - books - texts - movies
Black Trash Productions at home: http://www.blacktrash.org
Black Trash Productions on Facebook:
http://www.facebook.com/blacktrashproductions

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

Build for Windows Store.

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