TELNET Test POP3/IMAP4 connections

If for any reason the POP3/IMAP4 connection fails to authenticate, you can test a connection for either POP3 or IMAP4 via TELNET:

POP3 TEST:

The first set of instructions establishes whether you have (and therefore Supportworks will have) access to an account on an Internet mail server:

• 1..On the Supportworks server, run a Windows command prompt.

• 2..Enter the following to verify that you have POP3 access:

TELNET <mail server> 110

You should now be presented with a banner informing you that you have connected to the mail server.

• 3..If the above is successful, enter the following in the case of POP3:
• USER <username>
• PASS <password>
• LIST

where <username> is the login ID for the relevant account on the mail server, and <password> is the required password.

If you can now see a list (POP3) or the number (IMAP4) of valid email messages within the account's Inbox (assuming such messages have been received), this proves that you have access to either a POP3 or IMAP4 service account. You should now disconnect from the mail server (QUIT or 3 LOGOUT, as appropriate) and close the command prompt window.

If unsuccessful, the DBA would need to be consulted to make the necessary changes to the Exchange server or provide alternative authentication details.

IMAP4 TEST:

• 1..On the Supportworks server, run a Windows command prompt.

• 2..Enter the following to verify that you have IMAP4 access:

TELNET <mail server> 143

You should now be presented with a banner informing you that you have connected to the mail server.

• 3..If the above is successful, enter the following:

1 LOGIN <username> <password> 2 SELECT INBOX

where <username> is the login ID for the relevant account on the mail server, and <password> is the required password.

If you can now see a list of valid email messages within the account's Inbox (assuming such messages have been received), this proves that you have access to either a IMAP4 service account. You should now disconnect from the mail server (QUIT or LOGOUT, as appropriate) and close the command prompt window.

If unsuccessful, the DBA would need to be consulted to make the necessary changes to the Exchange server or provide alternative authentication details.