On 2021-10-22, Viktor Dukhovni via Exim-dev <exim-dev@exim.org> wrote: >> On 22 Oct 2021, at 11:45 am, admin--- via Exim-dev <exim-dev@exim.org> wrote: >> >> For what it's worth, by experience, you should avoid sending anything to any >> yahoo domains using pipelining. They will just retaliate on you if you do it, >> they will, for example, greylist the servers using pipelining but will allow >> the other ones. >> If this is really an exim bug, it's still worth correcting it, but you should >> really disable pipelining to yahoo, even when this bug will be resolved. > > Why would they bother advertising PIPELINING, if they don't > actually mean to tolerate its use? That does not seem right... >
BINARYMIME RFC3030 (https://datatracker.ietf.org/doc/html/rfc3030#section-4.2) doesn't show pipelined BDAT: the sender synchronises before sending body data. Dropping the connection seems like a resonable response to such a synchronisation error. PIPELINING RFC2920 (https://datatracker.ietf.org/doc/html/rfc2920) synchrionises the pipeline before any message content is trasmitted (the "DATA" command is allowed but the sender must wait for "354" before sending content) -- Jasen. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
