Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.unix.programmer > #16456
| Path | csiph.com!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail |
|---|---|
| From | Winston <wbe@UBEBLOCK.psr.com.invalid> |
| Newsgroups | comp.unix.bsd.freebsd.misc, comp.unix.programmer, comp.misc |
| Subject | Re: outgoing tcp port 25 blocked? how to prove it? |
| Date | Fri, 18 Oct 2024 20:18:36 -0400 |
| Organization | A noiseless patient Spider |
| Lines | 23 |
| Message-ID | <yded4dhrmr.fsf@UBEblock.psr.com> (permalink) |
| References | <87o73h4if7.fsf@tudado.org> |
| MIME-Version | 1.0 |
| Content-Type | text/plain |
| Injection-Date | Sat, 19 Oct 2024 02:18:37 +0200 (CEST) |
| Injection-Info | dont-email.me; posting-host="bfdef503d51b9d540957bb0df1bf0cd3"; logging-data="3713905"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/2oO4n4xjHB5dXYHX176O/" |
| User-Agent | Gnus/5.13 (Gnus v5.13) |
| Cancel-Lock | sha1:wUcOgkiHUj8LmmZ8NxEBC/UmL3Q= sha1:FlPRClwxJ7chY4xEgtrLviQNtZ8= |
| Mail-Copies-To | never |
| Xref | csiph.com comp.unix.bsd.freebsd.misc:4046 comp.unix.programmer:16456 comp.misc:25907 |
Cross-posted to 3 groups.
Show key headers only | View raw
Lesley Esen <lesen@wimezu.com> writes: > # tcpdump -n port 25 > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on ena0, link-type EN10MB (Ethernet), capture size 262144 bytes > 09:01:45.939473 IP 172.26.5.226.37963 > 69.164.210.174.25: Flags [S], seq 1665376094, win 65535, 172.26.*.* is private, not public, IP address space. If that's the TCP source address being sent to the remote hosts, it's not surprising you're not getting an answer. If I'm reading your article right, the public IP address 34.197.192.71. If you can't solve the problem directly, you may need to relay outbound mail via some AWS mail forwarder, if they have them. > The host 69.164.210.174 also runs an SMTP server, but someone seems to > block my path to it. It might not AWS as I also can't reach it from my > personal computer (with a dynamic IP address). Try "netstat -an4" on 69.164.210.174 to verify that the mail server is indeed listening on port 25. Also, if that host is behind a NAT firewall, you may also need to configure the firewall to enable port forwarding for port 25. -WBE
Back to comp.unix.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
outgoing tcp port 25 blocked? how to prove it? Lesley Esen <lesen@wimezu.com> - 2024-10-18 11:03 -0300
Re: outgoing tcp port 25 blocked? how to prove it? Winston <wbe@UBEBLOCK.psr.com.invalid> - 2024-10-18 20:18 -0400
Re: outgoing tcp port 25 blocked? how to prove it? Lesley Esen <lesen@wimezu.com> - 2024-10-19 09:11 -0300
Re: outgoing tcp port 25 blocked? how to prove it? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-10-19 07:33 -0700
Re: outgoing tcp port 25 blocked? how to prove it? Lesley Esen <lesen@wimezu.com> - 2024-10-19 13:13 -0300
Re: outgoing tcp port 25 blocked? how to prove it? John Levine <johnl@taugh.com> - 2024-10-19 18:40 +0000
Re: outgoing tcp port 25 blocked? how to prove it? Lesley Esen <lesen@wimezu.com> - 2024-10-19 19:13 -0300
Re: outgoing tcp port 25 blocked? how to prove it? Bob Eager <news0009@eager.cx> - 2024-10-19 19:43 +0000
csiph-web