Using Telnet to Troubleshoot Email Connectivity
PeteHalbeisen 060001VQWA Visits (1445)
Occasionally we receive PMRs related to Email Listener connectivity and after having the customer do a simple test using telnet, they're able to isolate the difficulty outside of Maximo (and the JavaMail API).
Examples of problems raised as PMRs include refused connections, timeouts, and invalid credentials.
The following three scenarios (POP3, IMAP, SMTP) will address how to validate protocol connectivity using basic authentication. Communication with your email server may differ slightly from these examples and a quick web search should get you on the right track.
Note: It's possible you may not be able to backspace in these sessions to correct typos. If that occurs, retype the command correctly on a new line.
telnet <popserver-address> 110
For this scenario you may need to base 64 encode your username and password. Encoders (and decoders) are readily available on the web.
Note that: "VXNlcm5hbWU6" decodes to "Username:"
Verify that the correct credentials are entered in the right format. Sometimes the email short name is a valid credential but the full email address is not. Make sure you're using the format in the Listener configuration that your email server expects.
It's also the case that email servers can be configured to only allow connectivity via certain email clients or IP address ranges. If you experience connectivity issues via telnet, work with your email server administrator to track down the problem.
To isolate secure connection problems, try using a secure utility such as openssl. This may be the subject of a future blog article.