You will note that when you telnet without specifying the port it resolves the name, but when you add the port the name resolution fails.
Try doing your telnet without the colon. The colon is being treated as part of the hostname. Use a space instad of the colon. You also do not need any username or password for authentication with SMTP, so you can skip the -l and the related username. For example:
telnet stout.m5hosting.com 25
If this is a shared hosting account, your host is being pretty cool to open SMTP on port 26 for you. I just did a telnet mail.hardboot.org on port 25 and 26, and got a SMTP banner on both no problem. I do not use SBC DSL, so I don't know if they are filtering port 25 like some other access providers. But, that's what I suspect given your description and that I am on a network that is not filtered and can get to both port 25 and port 26.
At 08:24 PM 3/25/2005 -0800, you wrote:
I'm trying to track down the problem I'm having with sending mail from my home computer through SBC DSL, to my non-SBC-hosted mail server. For some reason, I can receive email, but I can't send it. My web hoster has allowed me to use port 26 as well, and it works from my email program. I can send mail to myserver:26, but not myserver:25.
Can anyone give me some suggestions on finding out what's causing this? My first thought is that it's my hoster. But my hoster, of course, gives me a nice, bland, corporate poker face and says it's not them, and that it could be my ISP. I've tried connecting to the mail server via telnet from my own computer at home and from the server itself.
==============From my home computer I get:
localhost ~ $ telnet -l [EMAIL PROTECTED] mail.hardboot.org Trying 147.202.33.153... telnet: Unable to connect to remote host: Connection refused
localhost ~ $ telnet -l [EMAIL PROTECTED] mail.hardboot.org:25 telnet: could not resolve mail.hardboot.org:25/telnet: Temporary failure in name resolution
localhost ~ $ telnet -l [EMAIL PROTECTED] mail.hardboot.org:26
telnet: could not resolve mail.hardboot.org:26/telnet: Name or service not known
==============From my hosting account I get:
-bash-2.05b$ telnet -l [EMAIL PROTECTED] mail.hardboot.org Trying 147.202.33.153... telnet: connect to address 147.202.33.153: Connection refused
-bash-2.05b$ telnet -l [EMAIL PROTECTED] mail.hardboot.org:25 telnet: mail.hardboot.org:25: Name or service not known mail.hardboot.org:25: Unknown host
-bash-2.05b$ telnet -l [EMAIL PROTECTED] mail.hardboot.org:26 telnet: mail.hardboot.org:26: Name or service not known mail.hardboot.org:26: Unknown host
============== >From a third-party server I only have ssh available, and it gives me this:
u35610167:~ > ssh -l [EMAIL PROTECTED] mail.hardboot.org [EMAIL PROTECTED]@mail.hardboot.org's password: Permission denied, please try again.
u35610167:~ > ssh -l [EMAIL PROTECTED] mail.hardboot.org:25 ssh: mail.hardboot.org:25: Name or service not known
u35610167:~ > ssh -l [EMAIL PROTECTED] mail.hardboot.org:26 ssh: mail.hardboot.org:26: Name or service not known
Where do I go from here to isolate this problem? I really don't put it past SBC to do something this stupid, but it seems more likely to be a problem with my hoster.
-todd -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
-- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
