unable to use port25, always get a no route to host
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
unable to use port25, always get a no route to host
I have not been able to send mail, but i am able to receive it. That's what has brought me to this question. every time i try and send mail i get 'no route to host', but i am able to receive it fine. I have tried flushing my iptables and everything seems configured right in my mozilla mail client. What is strange is up untill I started running up2date, everything was fine. I've even tried telneting to other mail servers on port 25 and that doesn't work. can anyone help?
hmm, this could be firewall, routing, or dns related. Do you get no route to host messages when you try to telnet or pop3 to say, mail.somewhere .com only, or do you get the same message if you try to connect via the remote's ip address as well? Try the ip, if that works then it is probably DNS related. Check your routing table for anything odd also. Sounds like you have eliminated your firewall as a problem, but if you are behind another firewall box or appliance or a proxy, you will need to look there as well
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.