Troubleshoot SMTP server
If you are having problems connecting/using an SMTP server with LiveCycle, you should manually check that you can indeed connect and send e-mails by issuing the following set of commands on the server you want to connect from.
In this example, assuming you want to troubleshoot the connection to the SMTP server mail.company.com from a Windows server, you would issue the following from a command prompt:
cmd> telnet mail.company.com 25 220 mail.company.com ESMTP Sendmail 8.13.3/8.13.3; Fri, 3 Mar 2006 17:22:29 GMT helo mydomain.com 250 mail.company.com Hello bla-dhcp-206.company.com [<ip address>], pleased to meet you mail from: email@example.com 250 2.1.0 firstname.lastname@example.org… Sender ok rcpt to: email@example.com 250 2.1.5 firstname.lastname@example.org… Recipient ok data 354 Enter mail, end with '.' on a line by itself Text of the message . 250 2.0.0 k23HMTO3006628 Message accepted for delivery quit 221 2.0.0 mail.company.com closing connection Connection to host lost. cmd>
Preferably you should attempt to use the same e-mail addresses for the sender and recipients as the one that are meant to be used by your application. If any of the operations above fail, it means that the problem is NOT with your application, but with the SMTP server itself. If it works, then you should try the same from a remote host, to see if your issue might have to do with a firewall or some network issue.
If you don’t get any errors when doing these 2 operations, then it means that your server is properly set to send email, so now you can switch to troubleshooting POP.
Troubleshoot POP server
The POP3 manual commands are almost as easy as the SMTP commands. To check your mail with POP:
cmd> telnet popserver.somedomain.com 110 user <some_valid_user> pass <user_password> stat
Each of these commands should return “+OK”. The “stat” command should also return 2 numbers indicating the number of new messages received, and messages left on the server.