Advertisement

Seems no one really reads the Unix section anymore...

Started by March 18, 2005 12:17 PM
14 comments, last by markr 19 years, 8 months ago
Tracerouting mail.escuelaelectronica.org (domain hosted elsewhere.. I know the owner)


traceroute to escuelaelectronica.org (72.9.247.50), 30 hops max, 38 byte packets 1  216.69.174.243 (216.69.174.243)  0.136 ms  0.075 ms  0.055 ms 2  ip-64-202-160-18.secureserver.net (64.202.160.18)  0.426 ms  0.369 ms  0.347 ms 3  phv-edge-01.inet.qwest.net (65.121.90.65)  0.473 ms  0.652 ms  0.413 ms 4  bur-core-03.inet.qwest.net (205.171.13.6)  32.351 ms  32.352 ms  32.354 ms 5  lap-brdr-01.inet.qwest.net (205.171.213.106)  32.812 ms  32.810 ms  32.920 ms 6  bpr1-so-6-0-0.LosAngelesEquinix.savvis.net (208.174.196.13)  32.843 ms  32.784 ms  32.723 ms 7  dcr1-so-4-2-0.LosAngeles.savvis.net (208.172.44.105)  32.916 ms  32.814 ms  33.177 ms 8  dcr2-loopback.Atlanta.savvis.net (208.172.66.100)  84.694 ms  84.743 ms  84.672 ms 9  bpr2-so-0-0-0.AtlantaPaix.savvis.net (208.172.75.238)  84.617 ms  84.541 ms  84.574 ms10  208.173.60.218 (208.173.60.218)  77.053 ms  76.896 ms  76.954 ms11  209.51.131.25 (209.51.131.25)  76.998 ms  76.852 ms  76.803 ms12  65.254.48.2 (65.254.48.2)  77.156 ms  78.435 ms  83.806 ms13  72.9.247.50 (72.9.247.50)  77.044 ms  76.841 ms  77.028 ms


telnet to port 25

telnet mail.escuelaelectronica.org 25
Trying 72.9.247.50...
telnet: connect to address 72.9.247.50: No route to host
Could very well be your ISP. A lot of them don't allow outgoing traffic on port 25; this prevents machines from being used as spam zombies, or of actively spamming. This is sometimes even true of ISPs that should really allow this sort of thing.

Huh... thirty years ago, who would have believed that "spam zombie" would become a legitimate computer engineering term?
Advertisement
Quote: Original post by Sneftel
Could very well be your ISP. A lot of them don't allow outgoing traffic on port 25; this prevents machines from being used as spam zombies, or of actively spamming. This is sometimes even true of ISPs that should really allow this sort of thing.

Huh... thirty years ago, who would have believed that "spam zombie" would become a legitimate computer engineering term?


It's not my ISP. I have no problem sending mail from my computer :P.

As I've mentioned before, this is on a virtual dedicated server machine. Not my own.
Quote: Original post by Maega
As I've mentioned before, this is on a virtual dedicated server machine. Not my own.
And the ISP of this server may not allow it. ("ISP", in this case, can mean either the server facility or its bandwidth provider, though the former is much more likely.) All the signs are there: you can get ICMP through to the server, but you can't route to port 25, including through telnet, and you don't have any trouble with loopback on port 25. That strongly indicates that a router somewhere is refusing to route outgoing TCP/25 packets. I'm guessing that you won't have any problems finding a route if you try telnetting to other ports.
Quote: Original post by Sneftel
Quote: Original post by Maega
As I've mentioned before, this is on a virtual dedicated server machine. Not my own.
And the ISP of this server may not allow it. ("ISP", in this case, can mean either the server facility or its bandwidth provider, though the former is much more likely.) All the signs are there: you can get ICMP through to the server, but you can't route to port 25, including through telnet, and you don't have any trouble with loopback on port 25. That strongly indicates that a router somewhere is refusing to route outgoing TCP/25 packets. I'm guessing that you won't have any problems finding a route if you try telnetting to other ports.


Ah.. it appears you seem to be correct. The FAQ of the server provider mentions they have a relay server and ONLY says to use that unless you set up your own mail server.

I guess that isn't exactly true :D.

I tried telneting to 110 (POP3) and it let me through without a problem

I'll have to ask them what's up.

As I suggested before, the hosting provider have a policy of only allowing outbound relaying via THEIR relay.

Presumably this is so that they can keep tabs on what their customers are sending more easily, and detect spam, viruses or other undesirable content.

This is an excellent thing and you should be pleased (Unless you are a spammer of course).

Simply change Qmail's configuration so that it sends all email to this relay as a "Smart host" or similar.

Mark

This topic is closed to new replies.

Advertisement