On 13/03/2022 20:33, Jeremy Harris via Exim-users wrote:
On 13/03/2022 20:06, Mike Tubby via Exim-users wrote:
2022-03-13 19:47:53 1nTTGO-0001Jw-Tr
H=alt2.gmail-smtp-in.l.google.com [2a00:1450:4025:c03::1a]: SMTP
timeout after sending data block (476909 bytes written): Connection
timed out
On Sun, Mar 13, 2022 at 08:06:45PM +, Mike Tubby via Exim-users wrote:
> 2022-03-13 19:47:53 1nTTGO-0001Jw-Tr H=alt2.gmail-smtp-in.l.google.com
> [2a00:1450:4025:c03::1a]: SMTP timeout after sending data block (476909
> bytes written): Connection timed out
Looks like broken Path MTU discovery
On 13/03/2022 20:06, Mike Tubby via Exim-users wrote:
2022-03-13 19:47:53 1nTTGO-0001Jw-Tr H=alt2.gmail-smtp-in.l.google.com
[2a00:1450:4025:c03::1a]: SMTP timeout after sending data block (476909 bytes
written): Connection timed out
Google doesn't want to talk to you, at least on that IP.
I have started seeing odd timeouts from Exim when talking to Goolge
gmail, email path:
MTA (Thunderbird/Win 10) --> mail.tubby.org (Linux/Exim) -->
relay1.thorcom.net (Linux/Exim) --> Gmail
My MTA is behind my firewall, it sends SMTP to my public mail server,
which relays (smart host)
On 2022-03-13, The Doctor via Exim-users wrote:
> I was wonder if it is doable that the outside world
> can only see ports 587 and 465
> while limiting port 25 to localhost only.
assuming 192.0.2.44 is "the outside world" ip address.
in main configuration:
daemon_smtp_ports = 25 : 587 : 465
