On Fri, Oct 22, 2021 at 08:17:03PM -0000, Jasen Betts via Exim-dev wrote:
> >> 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)
The yahoo.co.jp domain advertises only PIPELINING not CHUNKING or
BINARYMIME:
< 250-mtagw7025.mail.djm.ynwp.yahoo.co.jp
< 250-PIPELINING
< 250-8BITMIME
< 250 SIZE 20480000
If they wanted to punish senders for *using* it, WTF advertise it?
--
Viktor.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim
details at http://www.exim.org/ ##
