Author: Rical Jasan Date: To: exim-users Subject: Re: [exim] Broken Pipe to Dovecot LMTP Socket
On 10/26/2016 03:01 AM, Jeremy Harris wrote: > On 26/10/16 08:42, Rical Jasan wrote:
>> Might the broken pipe be in reference to logwatch->exim and
>> not exim->dovecot?
>
> I doubt that. "Broken pipe" refers to the EPIPE error, which
> is specifically for an attempt to write on a pipe that has no
> reader. The reverse situation, reading on a pipe where the
> writer has closed, gets an end-of-file indication - zero bytes
> returned with no error.
>
> So it's the transport, in Exim terms.
I figured. I threw that idea in at the last minute, as I was writing.
Is there anything I can throw into the signal handler to dig deeper, or
do I need to look at either the system or Dovecot? It's strange that
the "Broken pipe" occurs several times in succession, the message is
ultimately delivered, but Exim still resends the message later.