> "Aaron Stone" <[EMAIL PROTECTED]> wrote: > > Exim simply should not be waiting for these responses before continuing on to > the next query. What version are you using? Are others using Exim experiencing > this same problem?
I am using Exim 4.34 and have found the problem. Contrary to some other information I found (probably outdated), Exim does fully support pipelining. However, there is a bug in which pipelining and other ESMTP options do not work when SMTP is used as a local (rather than remote) transport. There is a regex that is used to search for the "PIPELINING" status reply that does not get properly initialized in this case. > I don't think it would hurt anything to move the responses from the DATA > handler to the RCPT handler. The main issue with pipelining, as I understand > it, is that neither end should ignore the read side of a socket while writing > to it. Since the OS buffers for us, I can't see how this isn't a non-issue. No need to move the responses. I was off-base in my earlier message. After reading the RFC again, it is clear that the client does have to support pipelining for LMTP to work. And in fact, the RFC does suggest that the server should, in fact, buffer RCPT TO status codes and send them at once, just as dbmail-lmtpd does. Thanks for sending the input, which prodded me to dig into the Exim code a bit. David ____________________________________________________________________________ This message is spam and virus free. Filtering solutions by http://omd3.com Expert computer system support and development by http://baysidenetworks.com
