On Thu, Feb 04, 2021 at 02:57:43PM +0000, Paul Gregg via mailop wrote: > On Thu, Feb 04, 2021 at 12:03:45PM +0000, Paul Smith via mailop wrote: > > On 04/02/2021 11:39, Paul Gregg via mailop wrote: > > >It sounds like you are using PIPELINING when the remote doesn't support it > > >(properly). > > >See if you can turn off pipelining (at least to that endpoint) on your > > >client side. > > > > What is the server doing incorrectly with the pipelining? > > > > > > > 250 2.1.0 OK > > > > 250 2.1.5 OK > > > > 250 2.1.5 OK > > > > 452 4.5.3 Please resend separately > > > > 452 4.5.3 Please resend separately > > > > 250 2.1.5 OK > > > > 250 2.1.5 OK > > I'd expect the Server response to provide the rcpt to address in the address > per rfc2920 > > <quote> > C: EHLO dbc.mtview.ca.us > S: 250-innosoft.com > S: 250 PIPELINING > C: MAIL FROM:<mr...@dbc.mtview.ca.us> > C: RCPT TO:<n...@innosoft.com> > C: RCPT TO:<d...@innosoft.com> > C: RCPT TO:<k...@innosoft.com> > C: DATA > S: 250 sender <mr...@dbc.mtview.ca.us> OK > S: 250 recipient <n...@innosoft.com> OK > S: 250 recipient <d...@innosoft.com> OK > S: 250 recipient <k...@innosoft.com> OK > </quote> > > Absent the rcpt address in the server response, the client relies on the > server MUST respond to commands in the order they are > received - and the original post suggests that isn't the case either.
Replying to my own message. Went back and looked at the exim log from OP... seems the ordering was correct - so that means exim is screwing it up. I'd still recommend disabling pipelining on the client side. PG _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
