Jeremy Harris <jgh@???> (Mi 20 Sep 2017 10:18:41 CEST):
> Here's the relevant bit:
>
> On 19/09/17 23:46, SW & Work SaS wrote:
> > Connecting to smtp.thistledesign.it [46.252.149.139]:25 from 207.58.179.71
> > ... failed: Connection timed out (timeout=10m)
>
> It wasn't a delay-before-banner, it was a total lack of TCP response.
> Assuming it isn't lying and did actually wait ten minutes... there's
> nothing you can do about that apart from try some alternate means of
> contacting that system or its operators.
>
> My best guess would be that they have firewalled you. However, that
> and the above does not match your description of a telnet test.
> Was that test done from the exact same source IP? Is it repeatable now?
Maybe SW is right in some way.
I did a test, with a exim 4.89, Debian 9 package.
The firewall of the target host just drops the packets, for ipv4 as well as for ipv6.
16:12:22 set_process_info: 6006 delivering 1duPrv-0005Iz-Hs to hs12.schlittermann.de [2001:470:72aa:8::12] (info@???)
16:12:22 Connecting to hs12.schlittermann.de [2001:470:72aa:8::12]:25 ... 2001:470:72aa:8::12 in hosts_try_fastopen? no (option unset)
16:13:22 selecting on subprocess pipes
16:14:22 selecting on subprocess pipes
16:14:32 failed: Connection timed out (timeout=5m)
16:14:32 LOG: MAIN
16:14:32 H=hs12.schlittermann.de [2001:470:72aa:8::12] Connection timed out
16:14:32 set_process_info: 6006 delivering 1duPrv-0005Iz-Hs: just tried hs12.schlittermann.de [2001:470:72aa:8::12] for info@???: result DEFER
16:14:32 delivering 1duPrv-0005Iz-Hs to hs12.schlittermann.de [84.19.194.10] (info@???)
16:14:32 set_process_info: 6006 delivering 1duPrv-0005Iz-Hs to hs12.schlittermann.de [84.19.194.10] (info@???)
16:14:32 Connecting to hs12.schlittermann.de [84.19.194.10]:25 ... 84.19.194.10 in hosts_try_fastopen? no (option unset)
16:15:22 selecting on subprocess pipes
16:16:22 selecting on subprocess pipes
16:16:43 failed: Connection timed out (timeout=5m)
16:16:43 LOG: MAIN
16:16:43 H=hs12.schlittermann.de [84.19.194.10] Connection timed out
So, either the timestamps of the debug log are wrong (I didn't watch it
closely), or the timeout of 5m is reached by some other magic, I mean,
it looks like 130 seconds instead of 300 seconds, some OS imposed limit?
Best regards from Dresden/Germany
Viele Grüße aus Dresden
Heiko Schlittermann
--
SCHLITTERMANN.de ---------------------------- internet & unix support -
Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
gnupg encrypted messages are welcome --------------- key ID: F69376CE -
! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -
