| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision |
| usetelnettotestsmtpcommunication [2013/03/10 15:48] – deftesprit | usetelnettotestsmtpcommunication [2013/03/10 15:58] – deftesprit |
|---|
| * **Message body** This is a test message | * **Message body** This is a test message |
| |
| ^ Note: ^ | | ^ Note: ^ |
| | You should always use a valid sender e-mail address so that any non-delivery report (NDR) messages that are generated by the destination SMTP server are delivered to the sender of the message. || | | You should always use a valid sender e-mail address so that any non-delivery report (NDR) messages that are generated by the destination SMTP server are delivered to the sender of the message. | |
| |
| The commands in Telnet Client are not case-sensitive. The SMTP command verbs are capitalized for clarity. | The commands in Telnet Client are not case-sensitive. The SMTP command verbs are capitalized for clarity. |
| - At a command prompt, type**telnet**, and then press ENTER. This command opens the Telnet session. | - At a command prompt, type **telnet**, and then press ENTER. This command opens the Telnet session. |
| - 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.<br /> <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: ^ |
| - Type**EHLO contoso.com** and then press ENTER. | | 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**MAIL FROM:chris@contoso.com** and then press ENTER. | - Type **EHLO 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 **MAIL FROM:chris@contoso.com** and then press ENTER. |
| - 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 **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**Subject: Test from Contoso** and then press ENTER. | - Type **DATA** and then press ENTER. You will receive a response that resembles the following: |
| - Press ENTER. RFC 2822 requires a blank line between the ''Subject:'' header field and the message body. | <code>354 Start mail input; end with <CLRF>.<CLRF></code> |
| - Type**This is a test message** and then press ENTER. | - Type **Subject: Test from Contoso** 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. RFC 2822 requires a blank line between the "Subject:" header field and the message body. |
| - 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> | - Type **This is a test message** and then press ENTER. |
| - To close the Telnet session, type**quit** and then press ENTER. | - 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> |
| </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. |
| <!-- ApplyClick with current id --> <img alt''"" src''"http://i.msdn.microsoft.com/Global/Images/clear.gif" /> Evaluate the Results of a Telnet Session | |
| |
| | Evaluate the Results of a Telnet Session |
| |
| This section provides information about responses that may be provided to the following commands, which were used in the previous example: | This section provides information about responses that may be provided to the following commands, which were used in the previous example: |
| * EHLO contoso.com | * EHLO contoso.com |
| * MAIL FROM:chris@contoso.com | * MAIL FROM:chris@contoso.com |
| * RCPT TO:kate@fabrikam.com NOTIFY''success,failure | * RCPT TO:kate@fabrikam.com NOTIFYsuccess,failure |
| <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>The 3-digit SMTP response codes that are defined in RFC 2821 are the same for all SMTP messaging servers. The text descriptions may differ slightly for some SMTP messaging servers. In the previous example, the destination computer is running Exchange Server 2010.</td> </tr> </tbody> </table> </p> | ^ Note: ^ |
| | | The 3-digit SMTP response codes that are defined in RFC 2821 are the same for all SMTP messaging servers. The text descriptions may differ slightly for some SMTP messaging servers. In the previous example, the destination computer is running Exchange Server 2010. | |
| |
| <!-- ApplyClick with current id --> <img alt''"" src''"http://i.msdn.microsoft.com/Global/Images/clear.gif" /> Open mail1.fabrikam.com 25 | Open mail1.fabrikam.com 25 |
| |
| <strong>Successful Response</strong> <code>220 mail1.fabrikam.com Microsoft ESMTP MAIL Service ready at <day-date-time></code> | **Successful Response** <code>220 mail1.fabrikam.com Microsoft ESMTP MAIL Service ready at <day-date-time></code> |
| |
| <strong>Failure Response</strong> <code>Connecting to mail1.fabrikam.com...Could not open connection to the host, on port 25: Connect failed</code> | **Failure Response** <code>Connecting to mail1.fabrikam.com...Could not open connection to the host, on port 25: Connect failed</code> |
| |
| **Possible Reasons for Failure** | **Possible Reasons for Failure** |
| * An incorrect port number was specified. | * An incorrect port number was specified. |
| |
| <!-- ApplyClick with current id --> <img alt''"" src''"http://i.msdn.microsoft.com/Global/Images/clear.gif" /> EHLO contoso.com | EHLO contoso.com |
| |
| <strong>Successful Response</strong> <code>250 mail1.fabrikam.com Hello [<sourceIPaddress>]</code> | **Successful Response** <code>250 mail1.fabrikam.com Hello [<sourceIPaddress>]</code> |
| |
| <strong>Failure Response</strong> <code>501 5.5.4 Invalid domain name</code> | **Failure Response** <code>501 5.5.4 Invalid domain name</code> |
| |
| <strong>Possible Reasons for Failure</strong> There are invalid characters in the domain name. Alternatively, there are connection restrictions on the destination SMTP server. | **Possible Reasons for Failure** There are invalid characters in the domain name. Alternatively, there are connection restrictions on the destination SMTP server. |
| |
| |**<!--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:** | | ^ Note: ^ |
| | EHLO is the Extended Simple Message Transfer Protocol (ESMTP) verb that is defined in RFC 2821. ESMTP servers can advertise their capabilities during the initial connection. These capabilities include their maximum accepted message size and their supported authentication methods. HELO is the older SMTP verb that is defined in RFC 821. Most SMTP messaging servers support ESMTP and EHLO. | | | EHLO is the Extended Simple Message Transfer Protocol (ESMTP) verb that is defined in RFC 2821. ESMTP servers can advertise their capabilities during the initial connection. These capabilities include their maximum accepted message size and their supported authentication methods. HELO is the older SMTP verb that is defined in RFC 821. Most SMTP messaging servers support ESMTP and EHLO. | |
| |
| <!-- ApplyClick with current id --> <img alt''"" src''"http://i.msdn.microsoft.com/Global/Images/clear.gif" /> MAIL FROM:chris@contoso.com | MAIL FROM:chris@contoso.com |
| |
| <strong>Successful Response</strong> <code>250 2.1.0 Sender OK</code> | <strong>Successful Response</strong> <code>250 2.1.0 Sender OK</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. | <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. |
| |
| <!-- ApplyClick with current id --> <img alt''"" src''"http://i.msdn.microsoft.com/Global/Images/clear.gif" /> RCPT TO:kate@fabrikam.com NOTIFY''success,failure | RCPT TO:kate@fabrikam.com NOTIFY''success,failure |
| |
| <strong>Successful Response</strong> <code>250 2.1.5 Recipient OK</code> | <strong>Successful Response</strong> <code>250 2.1.5 Recipient OK</code> |
| <strong>Possible Reasons for Failure</strong> The specified recipient does not exist in the organization. | <strong>Possible Reasons for Failure</strong> The specified recipient does not exist in the organization. |
| |
| </div> | |
| |
| -- Main.FredPettis - 2010-06-25 | |
