10.3.1 Finding the Email Problem
Configuration and setup:
1. Are TCP/IP and MSF running?
2. Check the delivery schedule of the SMTP distribution queues.
3. If your recipient machine is an IBM i and you are using OfficeVision, is SNADS running?
4. Is your SMTP configuration correct? Have you nominated a Remote Name Server? Is the address of the Remote Name Server correct?
5. Has your IBM i exceeded the configured system storage threshold? It is usually shipped as 90%. The current usage can be checked by using command DSPSYSSTS.
Where to look:
If LANSA Email is not working, you can attempt to identify where the problem is by looking at:
1. The return code of the Email BIFs. If they return an error status, review the job log of the job where the LANSA function is running to read any diagnostic messages issued by LANSA.
2. The job log of the MSF job. The MSF job handles the processing of the mail message once it is written to MSF by LANSA. Review the job log to see if there is any indication of a problem.
3. The LANSA Email Tracing spooled file. This file traces the mail messages as they are processed by the MSF exit points. Refer to 10.3.2 LANSA Email Tracing for details about tracing LANSA Email messages.
4. The chapter in the explains how to send and receive mail with OfficeVision or with the SNDDST and RCVDST commands, if you don't have OfficeVision. You should ensure that SNDDST is set up and functions correctly before setting up LANSA Email.
Mail message options:
The mail message options PRIORITY, SENSITIVITY, IMPORTANCE and RECEIPT_REQUESTED may be ignored by some mail clients. If your application is only used within your organization, then you can verify that these options are being recognized. If you are sending mail messages over the Internet and you make these options available to the application users, it is your responsibility to advise them that these options may not be recognized.