Question & Answer
Question
I am installing CSSMTP on a test LPAR. I have been playing with the various configuration options, and trying to create mail messages from that system's JES2 spool environment that will allow me to test the various configuration options. However, I am apparently not creating the correct type of mail that will cause a deadletter scenario. What type of mail (created either by batch or SMTPNOTE) will cause that mail to be considered a dead letter?
Cause
CSSMTP determines that a mail message is a dead letter for the following reasons:
- An undeliverable mail notification cannot be returned to the originator.
- The original mail message was an undeliverable mail notification; therefore, the originator is not specified and the mail could not be sent to the recipient.
- An error report cannot be delivered to the mail administrators.
Answer
There are four necessary conditions for mail to be sent to the CSSMTP dead letter directory:
- In the CSSMTP configuration file, you must set the DeadLetterAction parameter on the UNDELIVERABLE statement to Store
- In the CSSMTP configuration file, you must set the DeadLetterDirectory parameter on the UNDELIVERABLE statement to a fully qualified z/OS UNIX file system directory name
- You create a mail message that can not be delivered to the recipient and can not be returned to the originator
- You need a TARGETIP server that is going to reject the mail
For more information, see "Customizing the CSSMTP configuration file to handle undeliverable mail" in z/OS Communications Server: IP Configuration Guide.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21460482