On Fri, Oct 22, 2021 at 10:34:20PM +0100, Simon Arlott via Exim-dev wrote:
> It is likely that pipelining the QUIT results in the connection being
> closed with outgoing data discarded. It's entirely possible that a
> stateful firewall decides not to allow the half-closed connection to
> transfer
It is likely that pipelining the QUIT results in the connection being
closed with outgoing data discarded. It's entirely possible that a
stateful firewall decides not to allow the half-closed connection to
transfer the remaining data.
A packet capture of this issue would be useful.
--
Simon
On Fri, Oct 22, 2021 at 08:17:03PM -, 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
On 2021-10-22, Viktor Dukhovni via Exim-dev wrote:
>> On 22 Oct 2021, at 11:45 am, admin--- via Exim-dev 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
> On 22 Oct 2021, at 11:45 am, admin--- via Exim-dev 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
https://bugs.exim.org/show_bug.cgi?id=2816
Renaud Allard changed:
What|Removed |Added
CC||ren...@allard.it
--- Comment #13 from Renaud
https://bugs.exim.org/show_bug.cgi?id=2822
--- Comment #6 from Ferry ---
Until they fix it, it might be wise to set the dhparams, load the referenced
ones from RFC7919 or not ignoring tls_dhparam.
Without it, it's broken.
--
You are receiving this mail because:
You are on the CC list for the
https://bugs.exim.org/show_bug.cgi?id=2822
Jeremy Harris changed:
What|Removed |Added
See Also||http://bugs.debian.org/9681
|
