Link to home
Start Free TrialLog in
Avatar of Jamie King
Jamie King

asked on

Telnet and CMD not recognizing commands

I've been trying to use telnet to send emails, but commands like MAIL TO are described as unrecognized. Any solutions?
Avatar of Dr. Klahn
Dr. Klahn

It is increasingly difficult to use Telnet to check anything except the simplest SMTP connections, because most sites use extensions, firewalls, context filtering and IP-based filtering to restrict spam.  SMTP connections must therefore be exact and precise, be quick with timing and responses, and conform to what the receiving MTA considers valid.

An example of the last can be found at Microsoft's web site regarding SMTP to Exchange MTAs.  The exchange is close to, but not quite "usual" SMTP, particularly as regards AUTH LOGIN and the encrypted usernames.

If you can show us a session log, it will be helpful.

As per Dr Klahn, please can you post a copy of the interaction.

I am assuming you are successfully submitting a HELO / EHLO, and getting a valid response?


Avatar of Michelangelo
Flag of Italy image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
This is one of my "go to" forums when trying to do testing with Telnet (mostly for exchange server)

telnet 25
220 Microsoft ESMTP MAIL Service, Version: 5.0.2195.5329 ready at Sun, 15
Sep 2002 23:51:06 +0200
250 Hello []
mail from:
250 2.1.0 OK
rcpt to:
250 2.1.5
354 Start mail input; end with .
subject: this is a test
Hi Daniel
I'm trying to test this connection from Telnet.
Let me know if you get this message.
250 2.6.0  Queued mail for delivery
221 2.0.0 Service closing transmission channel
Connection to host lost.
Press any key to continue...

Open in new window

The point in here is that "mail to" doesn't exist it would be "rcpt to" and "mail from"
Michaelangelo identified the issue.