Lodbrok.be
Command is telnet <servername> 25
On Win 9x and NT 3.5/4.0 Telnet client this done by selecting the "preferences" from the "terminal" pull down menu, and checking the local echo radio button. For Windows 2000 telnet client, issue command "set local_echo", from the telnet command prompt.
helo <your domain name><enter> response should be as follows 250 OK mail from: <your Email Address><enter> response should be as follows 250 OK - mail from <your Email address> rcpt to: <recipient address><enter> response should be as follows 250 OK - Recipient <recipient address> data<enter> response should be as follows 354 Send data. End with CRLF.CRLF To: <recipient's display name><enter> From: <your display name><enter> Subject: <Subject field of Email message><enter> <Enter you body text><enter><enter> . <enter> response should be as follows 250 OK quit<enter>
Command is telnet <servername> 110
On Win 9x and NT 3.5/4.0 Telnet client this done by selecting the "preferences" from the "terminal" pull down menu, and checking the local echo radio button. For Windows 2000 telnet client, issue command "set local_echo", from the telnet command prompt.
+OK Microsoft Exchange POP3 server version 5.5.2653.23 ready
user <nt_domain>\<nt_username>\<mailbox_alias> pass <password> note: Since local echo has been set, your password will appear on the telnet terminal window in plain text. list Displays a list of email messages retr <message number> Displays a specific message in the telnet terminal window dele <message number> Deletes a specific message Quit Closes telnet session
The information in this article applies to: * Microsoft Exchange Server, version 5.5 SUMMARY: Follow the steps below to ensure that you have proper IMAP4 connectivity to a mailbox located on Microsoft Exchange. NOTE: Press ENTER after you type each line: Start a Telnet session using the following command:
If this works, you see the following response from the server:
+OK Microsoft Exchange IMAP4rev1 server version x.x.x (F.Q.D.N.) ready
This begins the communication by initiating a login to the mailbox. Do not forget the "?" and (space) before the commands. You should see this response:
+OK LOGIN completed
This selects the appropriate mailbox. You should get the following response (this varies, depending on the number of messages in the mailbox):
* <#> EXISTS * <#> RECENT * FLAGS (\Seen \Answered \Flagged \Deleted \Draft) * OK [PERMANENTFLAGS (\Seen \Answered \Flagged \Deleted \Draft)] * OK [UNSEEN <#>] Is the first unseen message * OK [UIDVALIDITY 73] UIDVALIDITY value. ? OK [READ-WRITE] SELECT completed.
* 1 FETCH (FLAGS ( ) INTERNALDATE "25-JUN-1998 10:57:38 -500" RFC822.SIZE 417 ENVELOPE 9"Thu, 25 Jun 1998 10:57:33 -500" "Test" (("Administrator" NIL "Administrator" "microsoft.com")) (("Administrator" NIL "Administrator" "microsoft.com")) (("Administrator" "microsoft".com")) NIL NIL NIL
"219876E11AFBD111A43F00C04F8FECCA33D4@mail2.dns.microsoft.com"))
* ? OK FETCH completed.
This logs the user out of the IMAP session with the Exchange Server computer. You should see a similar message when you are successful:
? LOGOUT * BYE Microsoft Exchange IMAP4rev1 server version 5.5.2654.50 signing off ? OK LOGOUT completed.
NOTE : The version number may vary depending upon the Exchange Server Service Pack installed. The example above is with Exchange Server version 5.4 SP4 applied. If you can complete the above steps without error, any IMAP4 client conforming to RFC 2060 should be able to connect to the mailbox on the Exchange Server computer.