Path: eternal-september.org!news.eternal-september.org!feeder3.eternal-september.org!panix!.POSTED.panix2.panix.com!panix2.panix.com!not-for-mail
From: kludge@panix.com (Scott Dorsey)
Newsgroups: comp.misc
Subject: Re: outgoing tcp port 25 blocked? how to prove it?
Date: 19 Oct 2024 16:10:03 -0000
Organization: Former users of Netcom shell (1989-2000)
Lines: 18
Message-ID: <vf0lkr$anu$1@panix2.panix.com>
References: <87o73h4if7.fsf@tudado.org> <87jze51e7f.fsf@wimezu.com> <veu9kb$3bo5m$2@dont-email.me> <877ca519ph.fsf@wimezu.com>
Injection-Info: reader1.panix.com; posting-host="panix2.panix.com:166.84.1.2";
	logging-data="9099"; mail-complaints-to="abuse@panix.com"

In article <877ca519ph.fsf@wimezu.com>, Lesley Esen  <lesen@wimezu.com> wrote:
>Thanks.  That makes sense.  The output now makes sense.  Completely
>blocked right from the first hop.  Perhaps AWS did not actually unblock
>outbound tcp 25; perhaps they unblocked only inbound tcp 25.
>
>%tcptraceroute -n srv1.dorfdsl.de 25
>Selected device ena0, address 172.26.5.226, port 22831 for outgoing packets
>Tracing the path to srv1.dorfdsl.de (82.139.196.13) on TCP port 25 (smtp), 30 hops max
> 1  * * *
> 2  * * *
> 3  * * *

That looks like your machine is blocking it since you don't even see your
router.  Or else your router is blocking it.
--scott

-- 
"C'est un Nagra. C'est suisse, et tres, tres precis."