Re: error writing to filter (bogofilter)

Matthias Andree writes:

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

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

Build for Windows Store.

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

_______________________________________________
Courier-maildrop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/courier-maildrop

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)

iEYEABECAAYFAlHC4RkACgkQx9p3GYHlUOK1FgCeIlxCX+mV0lhZr3JQUzYx3oWF
zyYAn24qMauTfC1Hs2SJxUp7wGwXGq7W
=aMgV
-----END PGP SIGNATURE-----