Jeremy Harris <jgh@???> (Mi 21 Jun 2017 23:56:54 CEST):
> On 21/06/17 09:54, Kurt Jaeger wrote:
> >>> failed to read pipe from transport process 28932 for transport smtp: required size=2680 > remaining size=329 and unfinished=false
>
>
> > I have something similar now, too, sending from a FreeBSD exim site
> > to some external site, over TLS, with many recipients. But the error is:
> >
> > Failed writing transport result to pipe: Broken pipe
> >
> > So my question: is that the same problem ?
>
> Having the reader process get bitten by the bug will make it go away,
> and you'd expect that sort of error if the writer process had more to
> write. So yes, it's a good candidate.
Yes, it is the same problem, depending on who dies sooner, the error
message tells you about a died delivery process or the parent of the
delivery process dies because it gets insufficient data from the
delivery child.
I've fixed it and as soon as I'm convinced that it is really fixed, I'll
push my fixes to the repo.
Best regards from Dresden/Germany
Viele Grüße aus Dresden
Heiko Schlittermann
--
SCHLITTERMANN.de ---------------------------- internet & unix support -
Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
gnupg encrypted messages are welcome --------------- key ID: F69376CE -
! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -
