https://bugs.exim.org/show_bug.cgi?id=2806
--- Comment #5 from Jeremy Harris <jgh146exb@???> ---
There might be something different about the .123 host which allowed it
to give a definitive response. It's only seen in that one case, above.
But that doesn't tell us why the others fail.
The delivery line for 1mYHW2-0005qQ-fF does not show chunking used ("K" field).
In your cut-down transport (not router!) it would have been enabled, but a
manual probe of 202.93.78.239 doesn't show them advertising it so that probably
is not an issue.
[Also a lack of TLS support. Yuk. At least that means cipher changes are
not an issue]
I suspect we'll need at least (full) debug info for one of these failing
sends (to a *good* user not a nonexistent one), and we might have to go to
packet capture. Debug can be turned on in ACL, so can be done only for
yahoo.co.jp. Possible?
--
You are receiving this mail because:
You are on the CC list for the bug.
