On 2021-06-11 at 15:21:46 UTC-0400 (Fri, 11 Jun 2021 21:21:46 +0200)
Benny Pedersen <m...@junc.eu>
is rumored to have said:
On 2021-06-11 19:04, Bill Cole wrote:
One other possibility is that the on-host firewall is not configured
to allow inbound connections on port 465.
vpn client ip to postfix 0.0.0.0 or :: not needed
My understanding is that the OP is connected to a VPN that puts her onto
a privileged network and that she could see the SYN headed for port 465
on the Postfix server on "the firewall" which I understand to be a
machine distinct from the Win10 client or the (Linux, most likely)
Postfix server.
However, most modern widely-used Linux distributions come with some
on-host firewall, usually visible via iptables and maybe using some
grander framework like firewalld. The common (and wise) defaults for
such things do not usually allow connections from the outside (i.e.
anything other than the loopback) by default for anything other than
essential services (i.e. ssh.) Even when packaging systems try to be
smart about enabling listening ports when installing servers that
require them, that is likely to not be done for an MTA like Postfix,
which in many cases is only used as a MSA to get mail from local
accounts to other places. If one installs a Postfix package which does
not have a port 465 service enabled by default, it almost certainly will
also not include an iptables or firewall-cmd line in its install scripts
to open up port 465.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
