Hi!
> 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
> 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.
Then, the next question that comes to my mind is:
What stops us to read/write in chunks smaller than 512 bytes from/to
that pipe ?
Do we need the writes to be atomic to preserve msg boundaries or such ?
--
pi@??? +49 171 3101372 3 years to go !
