Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Bob Eager Newsgroups: comp.unix.bsd.freebsd.misc,comp.unix.programmer,comp.misc Subject: Re: outgoing tcp port 25 blocked? how to prove it? Date: 19 Oct 2024 19:43:23 GMT Lines: 22 Message-ID: References: <87o73h4if7.fsf@tudado.org> <87plnwz40w.fsf@wimezu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net 8UcNi5y5yxTCGKeEpXDxzwSvk5jF4WYN1gnKhk0Su70wt4ocFo Cancel-Lock: sha1:ChDnA2v0W5NWp/dygs0EzDAZbaE= sha256:XycrPQa54mQ48MTLwg787/qU3Mef3CF/Wrgr+iwnSv0= User-Agent: Pan/0.145 (Duplicitous mercenary valetism; d7e168a git.gnome.org/pan2) Xref: csiph.com comp.unix.bsd.freebsd.misc:4050 comp.unix.programmer:16461 comp.misc:25912 On Sat, 19 Oct 2024 09:11:11 -0300, Lesley Esen wrote: > That's the public IP address, yes. This is typical on the AWS network. > Each instance gets a private and a public IP address. I never see the > public IP address in the instance, but the packets must be being > rewritten by the AWS network because I can communicate with the outside > world just fine. AS a data point ... I ran an outbound mail server on an AWS instance (FreeBSD) for four years (I stopped because I now have fast access at home). It connected with a mail server run by me, though. So I wonder if it's your ISO blocking an AWS IP range. -- Using UNIX since v6 (1975)... Use the BIG mirror service in the UK: http://www.mirrorservice.org