James B. Byrne:
> postconf mail_version
> mail_version = 3.6.3
>
> OS FreeBSD-13.0p5
>
> I am in the process of transferring one of our MX services to a
> new host. During one of the test sessions against live traffic a
> connection to the final delivery host from the test service could
> be made. In consequence several messages resulted in a delayed
> delivery notice.
>
> It is these messages for which I am seeing SMTP connection refused
> from the original sending hosts.
>
> The diagnostic information that I have respecting a representative
> message is reproduced below. I just need to know if this is caused
> by something I can fix at my end or not. And if so then what the
> problem is. And if not then why these messages are being refused.
>
> In the maillog I see this:
>
> Jan 19 12:49:29 mx31 postfix/smtp[81175]: 14FDA745F9:
> to=<[email protected]>, relay=none, delay=2877,
> delays=2877/0.02/0.13/0, dsn=4.4.1, status=deferred (connect to
> alt4.gmail-smtp-in.l.google.com[66.102.1.27]:25: Connection refused)
The connect(2) system call returned ECONNREFUSED, which normally
means that the TCP SYN request got a TCP RST response.
> In the defer queue I see this:
Same information as logged.
For me, alt4.gmail-smtp-in.l.google.com does not resolve to
66.102.1.27, but instead to 142.250.153.26 (and some IPv6).
Wietse
