On Mon, 25 Oct 2021 16:54:56 -0400 Karl Semich <0xloem@gmail.com> wrote:
usually "no route to host" is from the x.x.x.x but is unrelated to the port.
I never really checked, but like I said, at first sight, it looks like it IS related to the port. I'm not going to bother looking at the manual, but you can if you want. It's error 113... At any rate, from here the 'host' is fine and there's nothing on port 25, or it's rejecting connections on port 25 and giving a misleading error on purpose. Second option is less likely.
it's possible it could appear related to the port due to random timing
or something could be intentionally triggering the not-usually-port-related error only attempts to connect to the port were made
yes. So you can try connecting. Since you're in the US you won't be discriminated based on country.
maybe routing has changed in the past ten years?
nah, it still is all the old arpanet stuff.
I'm having experiences like that, too.