Using the undeliverable mail notification for problem determination

  • If the error text captured in the undeliverable mail notification for the undeliverable mail is not enough to explain the problem, then review the log file that is generated under the started task by using the message-ID value that is found in the Subject: header and search through the log file to see how the mail message was processed.
  • If the problem appears in communicating with a target server, set the loglevel value to at least 39 to capture TCP/IP traces. This shows SMTP commands and remote SMTP server replies between the CSSMTP application and the IP network. Resend the mail message.
  • If the mail does not get sent and no undeliverable mail notification is returned to the originator of the mail, wait for CSSMTP to retry to send the mail message based on the configured RetryLimit statement values.
    If there is still no undeliverable mail notification, do the following checks:
    • Check the configuration file for the undeliverable statement DeadLetterAction. If the statement is set to DELETE, then the undeliverable mail notification was deleted. If DeadLetterAction is set to STORE, then check the z/OS® UNIX file system under the configured or default directory path.
    • Check the log file that was generated under the started task, by using the undeliverable mail notification message ID value to determine how the mail was processed. The following is the message ID for the undeliverable mail notification: 
      SMTP2.JOB00051.host2@ibm.com.Nov192008.134147.442406.1U
Parent topic: Mail problems