| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| usetelnettotestsmtpcommunication [2013/03/10 15:55] – deftesprit | usetelnettotestsmtpcommunication [2013/03/10 16:00] (current) – deftesprit |
|---|
| - Type **set localecho** and then press ENTER. This optional command lets you view the characters as you type them. This setting may be required for some SMTP servers. | - Type **set localecho** and then press ENTER. This optional command lets you view the characters as you type them. This setting may be required for some SMTP servers. |
| - Type **set logfile** _<filename>_. This optional command enables logging of the Telnet session to the specified log file. If you only specify a file name, the location of the log file is the current working directory. If you specify a path and a file name, the path must be local to the computer. Both the path and the file name that you specify must be entered in the Microsoft DOS 8.3 format. The path that you specify must already exist. If you specify a log file that doesn't exist, it will be created for you. | - Type **set logfile** _<filename>_. This optional command enables logging of the Telnet session to the specified log file. If you only specify a file name, the location of the log file is the current working directory. If you specify a path and a file name, the path must be local to the computer. Both the path and the file name that you specify must be entered in the Microsoft DOS 8.3 format. The path that you specify must already exist. If you specify a log file that doesn't exist, it will be created for you. |
| - Type **open mail1.fabrikam.com 25** and then press ENTER. \\ <p> <table border''"0"> <tbody> <tr> <th><!--src''[../local/note.gif]--><img alt''"Bb123686.note(en-us,EXCHG.140).gif" src''"http://i.technet.microsoft.com/Bb123686.note(en-us,EXCHG.140).gif" />Note: </th> </tr> <tr> <td>You can't use the backspace key after you have connected to the destination SMTP server within the Telnet session. If you make a mistake as you type an SMTP command, you must press ENTER and then type the command again. Unrecognized SMTP commands or syntax errors result in an error message that resembles the following:</td> </tr> </tbody> </table> </p> <div id''"ctl00_MTCS_main_ctl28_ctl00_ctl02_"> <p></p> <div dir''"ltr"> <pre id''"ctl00_MTCS_main_ctl28_ctl00_ctl02_code">500 5.3.3 Unrecognized command</code> </div> </div> | - Type **open mail1.fabrikam.com 25** and then press ENTER. \\ ^ Note: ^ |
| | | You can't use the backspace key after you have connected to the destination SMTP server within the Telnet session. If you make a mistake as you type an SMTP command, you must press ENTER and then type the command again. Unrecognized SMTP commands or syntax errors result in an error message that resembles the following: | <code>500 5.3.3 Unrecognized command</code> |
| - Type **EHLO contoso.com** and then press ENTER. | - Type **EHLO contoso.com** and then press ENTER. |
| - Type **MAIL FROM:chris@contoso.com** and then press ENTER. | - Type **MAIL FROM:chris@contoso.com** and then press ENTER. |
| - Type **RCPT TO:kate@fabrikam.com NOTIFY''success,failure** and then press ENTER. The optional NOTIFY command defines the particular delivery status notification (DSN) messages that the destination SMTP server must provide to the sender. DSN messages are defined in RFC 1891. In this case, you're requesting a DSN message for successful or failed message delivery. | - Type **RCPT TO:kate@fabrikam.com NOTIFY''success,failure** and then press ENTER. The optional NOTIFY command defines the particular delivery status notification (DSN) messages that the destination SMTP server must provide to the sender. DSN messages are defined in RFC 1891. In this case, you're requesting a DSN message for successful or failed message delivery. |
| - Type **DATA** and then press ENTER. You will receive a response that resembles the following:<br /> <div id''"ctl00_MTCS_main_ctl28_ctl00_ctl03_"> <p></p> <div dir''"ltr"> <pre id''"ctl00_MTCS_main_ctl28_ctl00_ctl03_code">354 Start mail input; end with <CLRF>.<CLRF></code> </div> </div> | - Type **DATA** and then press ENTER. You will receive a response that resembles the following: |
| | <code>354 Start mail input; end with <CLRF>.<CLRF></code> |
| - Type **Subject: Test from Contoso** and then press ENTER. | - Type **Subject: Test from Contoso** and then press ENTER. |
| - Press ENTER. RFC 2822 requires a blank line between the "Subject:" header field and the message body. | - Press ENTER. RFC 2822 requires a blank line between the "Subject:" header field and the message body. |
| - Type **This is a test message** and then press ENTER. | - Type **This is a test message** and then press ENTER. |
| - Press ENTER, type a period (**.** ) and then press ENTER. You will receive a response that resembles the following:<br /> <div id''"ctl00_MTCS_main_ctl28_ctl00_ctl04_"> <p></p> <div dir''"ltr"> <pre id''"ctl00_MTCS_main_ctl28_ctl00_ctl04_code">250 2.6.0 <GUID> Queued mail for delivery</code> </div> </div> | - Press ENTER, type a period (**.** ) and then press ENTER. You will receive a response that resembles the following: \\ <code>250 2.6.0 <GUID> Queued mail for delivery</code> |
| - To disconnect from the destination SMTP server, type**QUIT** and then press ENTER. You will receive a response that resembles the following:<br /> <div id''"ctl00_MTCS_main_ctl28_ctl00_ctl05_"> <p></p> <div dir''"ltr"> <pre id''"ctl00_MTCS_main_ctl28_ctl00_ctl05_code">221 2.0.0 Service closing transmission channel</code> </div> </div> | - To disconnect from the destination SMTP server, type**QUIT** and then press ENTER. You will receive a response that resembles the following: \\ <code>221 2.0.0 Service closing transmission channel</code> |
| - To close the Telnet session, type **quit** and then press ENTER. | - To close the Telnet session, type **quit** and then press ENTER. |
| </div> | |
| |
| Evaluate the Results of a Telnet Session | Evaluate the Results of a Telnet Session |
| MAIL FROM:chris@contoso.com | MAIL FROM:chris@contoso.com |
| |
| <strong>Successful Response</strong> <code>250 2.1.0 Sender OK</code> | **Successful Response** <code>250 2.1.0 Sender OK</code> |
| |
| <strong>Failure Response</strong> <code>550 5.1.7 Invalid address</code> | **Failure Response** <code>550 5.1.7 Invalid address</code> |
| |
| <strong>Possible Reasons for Failure</strong> There is a syntax error in the sender's e-mail address. | **Possible Reasons for Failure** There is a syntax error in the sender's e-mail address. |
| |
| <strong>Failure Response</strong> <code>530 5.7.1 Client was not authenticated</code> | **Failure Response** <code>530 5.7.1 Client was not authenticated</code> |
| |
| <strong>Possible Reasons for Failure</strong> The destination server does not accept anonymous message submissions. You receive this error if you try to use Telnet to submit a message directly to a Hub Transport server. | **Possible Reasons for Failure** The destination server does not accept anonymous message submissions. You receive this error if you try to use Telnet to submit a message directly to a Hub Transport server. |
| |
| RCPT TO:kate@fabrikam.com NOTIFY''success,failure | RCPT TO:kate@fabrikam.com NOTIFYsuccess,failure |
| |
| <strong>Successful Response</strong> <code>250 2.1.5 Recipient OK</code> | **Successful Response** <code>250 2.1.5 Recipient OK</code> |
| |
| <strong>Failure Response</strong> <code>550 5.1.1 User unknown</code> | **Failure Response** <code>550 5.1.1 User unknown</code> |
| |
| <strong>Possible Reasons for Failure</strong> The specified recipient does not exist in the organization. | **Possible Reasons for Failure** The specified recipient does not exist in the organization. |
| |
| |
