Can't reach port 25 (SMTP)

[Javier Mosqueda]

Hello:

I can not Send mail. I can do it with squirrel mail though it uses a different port. I can POP mail (get it).

I also tried "$ telnet mydomain.com 25" with "No route to host" but same command to port 110, it's successful.

default telnet (port 23 for shell session) works ok.

I finally sent through 1025 according to Knowledge Base (http://service.futurequest.net/index.php?_a=knowledgebase&_j=questiondetails&_i=546&nav=+%26gt%3B+%3Ca+href%3D%27index.php%3F_a%3Dknowledgebase%26_j% 3Dsubcat%26_i%3D8%27%3EEmail%3C%2Fa%3E+%26gt%3B+%3Ca+href%3D%27in dex.php%3F_a%3Dknowledgebase%26_j%3Dsubcat%26_i%3D64%27%3ESecure+ Email%3C%2Fa%3E), which makes me suppose there is a failure in port 25 of Qbert where my domain resides. I will test other ports just for fun, but please let me know if port 25 is actually off or I have some trouble with that port in my PC

Greetings.
Javier

[Bob]

Javier,

Port 25 is fine on QBERT and the other servers... It would be your ISP blocking access to Port 25 for any mail servers other then their own as is mentioned in the Why can I receive email, but not send any?" (http://Service.FutureQuest.net/kb165) Knowledgebase Article.

2. ISP is Blocking Port 25 If your ISP is blocking port 25, you may not be able to send email using your FutureQuest® account. Some ISPs do this so that you are forced to use their email servers when sending email, as an attempt to prevent spam. Some ISPs that have been known to block port 25 are MindSpring, Earthlink, and AT&T.

-Bob

[Javier Mosqueda]

Thanks Bob:

This is an interesting topic, because I was at my friend's house this afternoon, we both use the same ISP and same domain in FQ, just different accounts in either access (DSL + FQ). I can SMTP through port 25 in my PC, but my friend can not in his, so I left his mail client's SMTP (thunderbird) set to port 1025.

Is there any switch in Linux that I could be missing which could block port 25?

Merry Christmas

[Kevin]

It is possible in Linux to firewall off port 25 on outbound connections. Running 'iptables -L -n' would list all firewall rules (if any). As far as changing it goes that would vary depending on how the firewall is setup. I have never allowed a Linux distro to install any firewall rules so I have no idea if any would do that on a default install but it doesn't sound very far fetched.