On 07/03/2021 20:14, Viktor Dukhovni wrote:
> What Jeremy did not mention is that he's seeing interoperability
> issues (reportedly with Google and IIRC Yahoo) when pipelining
> "BDAT nnnn LAST<CRLF>QUIT<CRLF>".
Specifically, both of the two large providers I've noted giving
problems consistently drop the connection without giving a response
for the BDAT LAST.o
Google is fine with a QUIT pipelined after data-ending-in-dot
(tranditional non-CHUNKING); I've not had a chance to evaluate
yahoodns.net yet. Both are fine with non-pipelined QUIT and
BDAT (LAST).
If so, that's deeply broken, never mind the legality of following a BDAT LAST
with a QUIT. Nothing in the pipeling specification says it is OK for a
later command to in effect be evaluated out of order.
There's even text in RFC 5321 section 4.1.1.10 saying that you can't close the
connection prematurely.
Ned
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp