On 28/09/2022 10:59, Victor Sudakov via Exim-users wrote:
Maybe I'd be better off setting hosts_try_fastopen to ":" in Exim only, just in
case?
No, because other services on your system would still suffer
from the kernel bug.
--
Cheers,
Jeremy
--
## List details at
Jeremy Harris via Exim-users wrote:
> On 28/09/2022 08:40, Victor Sudakov via Exim-users wrote:
> > I wonder what I will lose if I leave net.ipv4.tcp_fastopen=0 on the
> > mail server (not very loaded)?
>
> Not much unless your system also runs a high rate of TCP connections for
> other services
On 28/09/2022 08:40, Victor Sudakov via Exim-users wrote:
I wonder what I will lose if I leave net.ipv4.tcp_fastopen=0 on the
mail server (not very loaded)?
Not much unless your system also runs a high rate of TCP connections for
other services (eg. web). The bug (it's in the Linux firewall)
Andrew C Aitchison wrote:
> On Wed, 28 Sep 2022, Victor Sudakov via Exim-users wrote:
>
> > Dear Colleagues,
> >
> > Has anyone had problems recently sending to aspmx.l.google.com ?
>
> Yes. This is a known issue
> https://bugs.exim.org/show_bug.cgi?id=2907
>
> The bug is not actually in
On Wed, 28 Sep 2022, Victor Sudakov via Exim-users wrote:
Dear Colleagues,
Has anyone had problems recently sending to aspmx.l.google.com ?
Yes. This is a known issue
https://bugs.exim.org/show_bug.cgi?id=2907
The bug is not actually in exim, but in Linux kernel TCP Fast Open code
Dear Colleagues,
Has anyone had problems recently sending to aspmx.l.google.com ?
Sending gets stuck with the following error:
2022-09-27 21:09:48 1od0Ew-002IUh-GS H=alt2.aspmx.l.google.com [64.233.171.27]
TLS error on connection (recv): Error in the pull function.
2022-09-27 21:09:48
