SMTP Commands Automatically entering returns

[NexLAN]

I'm not sure if I'm posting in the correct forum or not and if I'm not
will someone please guide me in the right direction here.

We have a strange issue going on here. At my desk and at a client's
desk when we go to a command prompt and type telnet smtp.domain.com
110 (or even 25) the banner will appear. Whenever I try to input any
commands it doesn't matter what I type after I type one letter an
automatic carriage return is input after the letter. This same thing
happens on the mail server as well. I'm running Windows XP and so is
the client. We have Windows 2003 on the server. Our mail server is a
POP3 mail server with multiple domains. It does not matter which
domain we try to telnet to we receive the same response.

Now, here is where it gets stranger. Two people currently in this
office run Windows Vista and can go to a command prompt and type in
the telnet commands without any problems.

Any ideas? I even installed Windows XP Service Pack 3 on my computer
for giggles to see if that would work and it did not. Any ideas or
suggestions would be greatly appreciated.

Thanks!

 

[F.H. Muffman]

I'm not sure if I'm posting in the correct forum or not and if I'm not

will someone please guide me in the right direction here.

We have a strange issue going on here. At my desk and at a client's
desk when we go to a command prompt and type telnet smtp.domain.com
110 (or even 25) the banner will appear. Whenever I try to input any
commands it doesn't matter what I type after I type one letter an
automatic carriage return is input after the letter. This same thing
happens on the mail server as well. I'm running Windows XP and so is
the client. We have Windows 2003 on the server. Our mail server is a
POP3 mail server with multiple domains. It does not matter which
domain we try to telnet to we receive the same response.

Now, here is where it gets stranger. Two people currently in this
office run Windows Vista and can go to a command prompt and type in
the telnet commands without any problems.

Any ideas? I even installed Windows XP Service Pack 3 on my computer
for giggles to see if that would work and it did not. Any ideas or
suggestions would be greatly appreciated.

What does this have to do with Microsoft Outlook? I'd post to a newsgroup
specific to your OS.

Or, get putty.exe and use that instead of telnet.

 

[NexLAN]

What does this have to do with Microsoft Outlook?  I'd post to a newsgroup
specific to your OS.

Or, get putty.exe and use that instead of telnet.

Microsoft Outlook is e-mail isn't it???? I specifically stated I
wasn't for sure what forum to post in. There is no need to have an
attitude.

We use telnet to find out the exact error message a client is
receiving because the errors in Microsoft Outlook aren't always very
specific. When you telnet you can actually see the exact error
message straight from the server.

 

[F.H. Muffman]

I'm not sure if I'm posting in the correct forum or not and if I'm

Microsoft Outlook is e-mail isn't it???? I specifically stated I
wasn't for sure what forum to post in. There is no need to have an
attitude.

Son, you haven't seen attitude. Trust me, what I said was not attitude.
You asked if someone would guide you in the right direction. I did. A
newsgroup specific to your OS.

We use telnet to find out the exact error message a client is
receiving because the errors in Microsoft Outlook aren't always very
specific. When you telnet you can actually see the exact error
message straight from the server.

That assumes that the error is coming from the server. If it isn't a server
issue, telnet isn't going to help.

Now, if you want assistance with an Outlook issue, please, feel free to ask.
I'm quite good when it comes to Outlook issues. Heck, I'm even good when
it comes to telnet issues. RFC821/822 were the first RFCs I ever read cover
to cover and reading a network trace is second nature. In fact, speaking
of network traces, that's an even better way to find out what's happening,
especially when dealing with a plain text protocol, because it actually deals
with seeing what Outlook is doing, and if it's a client issue *or* a server
issue, you'll find the problem, or at least a very good indication of it.

I stand by my suggestion to just use putty.exe. I gave up on MS' telnet
a long long time ago, back when backspace wasn't recognized and echo was
off by default, two major annoyances for a terminal guy like me.