This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SMTP network is unreachable on first attempt

So, odd thing happening.

When looking through my smtpd_main log for a (probably) unrelated issue, I noticed that I see "failed: Network is unreachable" towards the beginning of the SMTP server process, followed by some other stuff and then another connect attempt resulting in a valid connection.

Is this normal? Or do I have something goofed up?

XG is 17.5.5 MR-5,  MTA mode with gamil smarthost.

22464 changed uid/gid: remote delivery to [my email address] with transport=smarthost_smtp
22464   uid=0 gid=0 pid=22464
22464   auxiliary group list: <none>
22464 set_process_info: 22464 delivering 4atc6Z-9qL0As-r7 using smarthost_smtp
22464 T: smarthost_smtp: for [my email address]
22464 smarthost_smtp transport entered
22464   [my email address]
22464 hostlist:
22464   'gmail-smtp-msa.l.google.com' IP 2607:f8b0:400d:c07::6d port -1
22464   'gmail-smtp-msa.l.google.com' IP 173.194.204.108 port -1
22464 checking status of gmail-smtp-msa.l.google.com
22464 locking /sdisk/spool/output//db/retry.lockfile
22464 locked  /sdisk/spool/output//db/retry.lockfile
22464 EXIM_DBOPEN: file </sdisk/spool/output//db/retry> dir </sdisk/spool/output//db> flags=O_RDONLY
22464 returned from EXIM_DBOPEN: 0x9461438
22464 opened hints database /sdisk/spool/output//db/retry: flags=O_RDONLY
22464 dbfn_read: key=T:gmail-smtp-msa.l.google.com:2607:f8b0:400d:c07::6d:587
22464 dbfn_read: key=T:gmail-smtp-msa.l.google.com:2607:f8b0:400d:c07::6d:587:4atc6Z-9qL0As-r7
22464 EXIM_DBCLOSE(0x9461438)
22464 closed hints database and lockfile
22464 no message retry record
22464 gmail-smtp-msa.l.google.com [2607:f8b0:400d:c07::6d]:587 retry-status = usable
22464 2607:f8b0:400d:c07::6d in serialize_hosts? no (option unset)
22464 delivering 4atc6Z-9qL0As-r7 to gmail-smtp-msa.l.google.com [2607:f8b0:400d:c07::6d] ([my email address])
22464 set_process_info: 22464 delivering 4atc6Z-9qL0As-r7 to gmail-smtp-msa.l.google.com [2607:f8b0:400d:c07::6d] ([my email address])
22464 Connecting to gmail-smtp-msa.l.google.com [2607:f8b0:400d:c07::6d]:587 ... Relate with Firewall rule id: 1
22464 2607:f8b0:400d:c07::6d in hosts_try_fastopen? no (option unset)
22464 failed: Network is unreachable
22464 LOG: MAIN
22464   H=gmail-smtp-msa.l.google.com [2607:f8b0:400d:c07::6d]:587 Network is unreachable
2019-05-31 13:34:02.768 [22464] 4atc6Z-9qL0As-r7 H=gmail-smtp-msa.l.google.com [2607:f8b0:400d:c07::6d]:587 Network is unreachable
22464 set_process_info: 22464 delivering 4atc6Z-9qL0As-r7: just tried gmail-smtp-msa.l.google.com [2607:f8b0:400d:c07::6d] for [my email address]: result DEFER
22464 added retry item for T:gmail-smtp-msa.l.google.com:2607:f8b0:400d:c07::6d:587: errno=101 more_errno=0,A flags=2
22464 address match test: subject=*@gmail-smtp-msa.l.google.com pattern=*
22464 gmail-smtp-msa.l.google.com in "*"? yes (matched "*")
22464 *@gmail-smtp-msa.l.google.com in "*"? yes (matched "*")
22464 checking status of gmail-smtp-msa.l.google.com
22464 locking /sdisk/spool/output//db/retry.lockfile
22464 locked  /sdisk/spool/output//db/retry.lockfile
22464 EXIM_DBOPEN: file </sdisk/spool/output//db/retry> dir </sdisk/spool/output//db> flags=O_RDONLY
22464 returned from EXIM_DBOPEN: 0x9461438
22464 opened hints database /sdisk/spool/output//db/retry: flags=O_RDONLY
22464 dbfn_read: key=T:gmail-smtp-msa.l.google.com:173.194.204.108:587
22464 dbfn_read: key=T:gmail-smtp-msa.l.google.com:173.194.204.108:587:4atc6Z-9qL0As-r7
22464 EXIM_DBCLOSE(0x9461438)
22464 closed hints database and lockfile
22464 no message retry record
22464 gmail-smtp-msa.l.google.com [173.194.204.108]:587 retry-status = usable
22464 173.194.204.108 in serialize_hosts? no (option unset)
22464 delivering 4atc6Z-9qL0As-r7 to gmail-smtp-msa.l.google.com [173.194.204.108] ([my email address])
22464 set_process_info: 22464 delivering 4atc6Z-9qL0As-r7 to gmail-smtp-msa.l.google.com [173.194.204.108] ([my email address])
22464 Connecting to gmail-smtp-msa.l.google.com [173.194.204.108]:587 ... Relate with Firewall rule id: 1
22464 173.194.204.108 in hosts_try_fastopen? no (option unset)
22464 connected
22464 read response data: size=53
22464   SMTP<< 220 smtp.gmail.com ESMTP b19sm3835827qkk.51 - gsmtp
22464 173.194.204.108 in hosts_avoid_esmtp? no (option unset)
22464   SMTP>> EHLO Sophos
22464 cmd buf flush 13 bytes
22464 read response data: size=170
22464   SMTP<< 250-smtp.gmail.com at your service, [71.117.162.129]
22464          250-SIZE 35882577
22464          250-8BITMIME
22464          250-STARTTLS
22464          250-ENHANCEDSTATUSCODES
22464          250-PIPELINING
22464          250-CHUNKING
22464          250 SMTPUTF8

 



This thread was automatically locked due to age.
Parents Reply
  • The one's you have highlighted are the same I was seeing, which is basically the a failure to route IPV6.  This doesn't bother me so much since I have not done any IPV6 configuration in my network. One day when I have time...

    Anyway, you are seeing so many of these apparently because with the follow-up IPV4 call succeeds, the destination is throwing an error. This causes the XG MTA to try the process again, starting back with the IPV6 lookup.

    Thanks,

    -GP

Children
No Data