|
|
T01SM011IT01SM089IT01SM096IT01SM112E
This chapter describes messages issued by the SMTP Mail Server. These messages include T01SM001 through T01SM999.
Explanation This message is confirmation that the shutdown request was received. The task group initiates orderly shutdown procedures. string is the I/O error detail information
Explanation The task group is ready to terminate. The shutdown procedures either completed in an orderly manner or were forced by another shutdown command. err_text is the MENU item error and err_item is the MENU item in error.
Explanation Failure to activate Ptask name, normally APILOGTA. err_text is the PARM item error and err_item is the PARM item in error.
Recommended Action This is an internal problem. Notify Customer Support.
Explanation This message indicates that commutator startup is resumed after waiting for some other event. This message follows T01SM019I. dom_name is the domain name in error.
Bad foreign domain dom_name Explanation There is an invalid SSMTP FROM= parameter. The FROM= parameter is to override the domain name (dom_name) on the HELO command. The message is written to the error log.
Recommended Action The FROM= parameter is part of a testing facility within Cisco IOS for S/390. This message should never appear in the log. The dom_name is the test domain that should replace domain name on an HELO command. Contact Customer Support.
SMTP Receiver starting for host rhostExplanation The SSMTP receiver is starting between the local host and remote host. The message is written to the event log.
T01SM011IWrite error to foreign host: reasonExplanation SSMTP has trouble communicating with a foreign host. The reason parameter is the reason why it failed. The message is written to the error log. Read "perror Messages" in Cisco IOS for S/390 Unprefixed Messages and Codes for more information.
Recommended Action The reason should direct your actions.
SYSOUT alloc failed: reasonExplanation SSMTP tries to allocate a mail spool file and fails. The reason why it failed is given (reason). The message is written to the error log. Read "perror Messages" in Cisco IOS for S/390 Unprefixed Messages and Codes for more information.
Recommended Action The reason should direct your actions.
Bad HELO command - no domain given Explanation The HELO command sent to the inbound mail handler did not contain a domain. All mail HELO commands should contain a valid principal host domain name. This is a clear violation of the RFC 1123 MAIL specification. This message is a warning; mail processing for the session continues.
Recommended Action The Cisco IOS for S/390 administrator should examine the T01LOG to see if it can be determined which Mailer is in violation of the MAIL protocol specifications. The Cisco IOS for S/390 administrator should then report the problem to Customer Support.
HELO command domain truncated Explanation The HELO command sent to the inbound mail handler contained a domain name that was greater than 64 characters. Cisco IOS for S/390 mail handler uses only the first 64 characters of the domain name for its processing. This message is a warning; mail processing for the session continues.
VALIDATION FAILED FOR CHAR/DBCS TRANSLATION MODULE modExplanation An invalid character set translation table (mod) has been specified or defined. This table may have been created incorrectly or was not created for the specified transopt (single or double).
Recommended Action Verify character set matches the translation mode.
Explanation This message appears immediately before an ABEND issued by the ACLOAD routine in ACCOM when a PLOAD macro specifies a module (module) not usable for subsequent processing. Unless local modifications are made to the Cisco IOS for S/390 distribution libraries, this message should only appear during testing, not in a product environment.
The code of the subsequent ABEND identifies the reason:
| 706 | The module is linked as non-executable. |
| C06 | The module is not found in the correct library, or is linked to be either overlay or scatter. |
| D06 | An error occurred during the BLDL process. |
Recommended Action The Cisco IOS for S/390 LOAD library must be in the STEPLIB DD statement of the Cisco IOS for S/390 startup JCL. If the ABEND code is a D06 and the module name is ARPAINIT, probably the LOAD library was not placed into (or was removed from) the STEPLIB DD statement in the startup JCL.
In most cases a relink with the correct attributes corrects this condition. The D06 ABEND is triggered by system action, and may require the assistance of a system programmer to resolve.
Recommended Action The LOG/ACCT file could not be opened.
Explanation The received file size filesize was greater than the DIVERT limit divert_lim. The file will be diverted as specified in the DIVERT parameter in APPCNFG.
Bad HELO command - invalid domain: domExplanation The HELO command sent to the inbound mail handler contained invalid characters in the domain name. All mail HELO commands should contain a valid principal host domain name. This message is a warning; mail processing for the session continues.
Recommended Action The Cisco IOS for S/390 administrator should examine the T01LOG to determine which Mailer is in violation of the MAIL protocol specifications and call Customer Support.
CANNOT PLOAD SMTPUSR Explanation Module SMTPUSR cannot be loaded from the STEPLIB DD libraries. This message is a warning; mail processing for the session continues.
Recommended Action The Cisco IOS for S/390 administrator should examine the STEPLIB DD libraries for the module. Regenerate SMTPUSR if missing.
RCPT TO User: user replaced with table entry tableExplanation SSMTP processed a RCPT TO mail command for inbound mail. Exit SMTPUSR replaced the specified user name with the specified table entry. Exit SMTPUSR lets a user name be mapped into a TSO user ID. This is an informational message to keep track of a RCPT TO user being changed by exit SMTPUSR.
MAIL RCVR: Discard partial message Explanation The input mail file receives an unexpected EOF or an input error. This message is written to the error log. All partially generated mail files are deleted.
... RCVD: time HOST:host m lines n charsExplanation SSMTP receives a mail message from the specified host. The message is written to the accounting log.
| time | The time at which the mail message is diverted. |
| host | The host from which the mail message is diverted. |
| m | The length of the mail message in lines. |
| n | The length of the mail message in characters. |
MAIL COPY: to printer Explanation SSMTP sends a mail message to the printer. The message is written to the event log.
Write error on temporary file: reasonExplanation SSMTP has trouble writing a mail file on the JES spool. reason is the reason it failed. The message is written to the error log. Read "perror Messages" in Cisco IOS for S/390 Unprefixed Messages and Codes for more information.
Recommended Action The reason should direct your actions.
MAIL DIVERTED: time HOST:host m lines n chars Explanation SSMTP is diverting a mail message to the printer from a host. The APPCFGxx parameter that may cause mail to be diverted to a printer is "DIVERT=" in the SMTP statement. The message is written to the accounting log.
| time | The time at which the mail message is diverted. |
| host | The host from which the mail message is diverted. |
| m | The length of the mail message in lines. |
| n | The length of the mail message in characters. |
Explanation The Mail RCVR session ended before completing.
No host found in RCPT TO: textExplanation The inbound mailer received a RCPT TO command in which the text (text) contains improper syntax. There was no @ in the text. It cannot be determined to which host the mail is to be directed. The RCPT TO command is rejected.
RCPT TO command host host is not our host Explanation SSMTP processed a RCPT TO mail command for inbound mail. The specified host address (host) on the RCPT TO mail command is different from Cisco IOS for S/390 host domain. The RCPT TO command is accepted and this informational message is written into the log.
Recommended Action The Cisco IOS for S/390 administrator should decide whether or not another host is mistakenly sending mail to its system and react accordingly.
Alias host:host sent on RCPT TO command Explanation SSMTP processed a RCPT TO mail command for inbound mail. The specified host (host) on the RCPT TO mail command is actually an alias name for the host. SSMTP accepts the RCPT TO command.
Recommended Action The Cisco IOS for S/390 administrator should decide whether or not the host is actually an alias as defined by the domain name resolver. If it is an alias, contact the postmaster of the sender of the mail message to change their host definition for your host. Sending of an alias in a RCPT TO mail command violates the SMTP protocol specifications.
Host: host Lookup error is:ac.ec message, Diag=x'code' Explanation A GET HOST BY NAME call to DNR for the specified host failed. Read "DNR Return Codes" in Cisco IOS for S/390 Unprefixed Messages and Codes for more information on action, error, and diagnostic codes.
| host | The host name. |
| ac | The action code. |
| ec | The error code. |
| message | Message text for the action and error codes. |
| code | The diagnostic code. |
Recommended Action The error message and codes should direct a user's action.
Host: host Lookup error return code: rcExplanation A GET HOST BY NAME call to DNR for the specified host. Module GETHBDNR was unable to accommodate the request and returned the specified error code.
| host | The host for which the call failed. |
| rc | The error code:
-2 - Bad arguments were passed to GETHBDNR -4 - No core was available for the request -5 - A software error occurred when processing the DIRSRV call in GETHBDNR. |
Recommended Action This error could be temporary or indicative of other problems within Cisco IOS for S/390. If the problem persists, check for related SVC dumps that may have been issued. The T01LOG and JES log of the job should be saved. Contact the Technical Response Center.
Host: host Lookup error is:ac.ec message, Diag=x'code' Explanation A GET HOST BY NAME call to DNR for the specified host failed. Read "DNR Return Codes" in Cisco IOS for S/390 Unprefixed Messages and Codes for more information on action, error, and diagnostic codes.
| host | The host name. |
| ac | The action code. |
| ec | The error code. |
| message | Message text for the action and error codes. |
| code | The diagnostic code. |
Recommended Action The error message and codes should direct a user's action.
SSMTP HELO Validation failed for host: hostExplanation The HELO command sent to SSMTP contains a host (host) not in the host names table (ARPINAMS). The message is written to the error log.
Recommended Action Save all output from the Cisco IOS for S/390 job. Get the list of commands entered by the user that generated this error.
If the problem is an unknown or undefined host, check that the host is in the Cisco IOS for S/390 Host Names Table. Insert the needed host entry if necessary and reassemble the Host Names Table. Ignore this message if the user inadvertently entered a nonexistent host.
Retry the operation. If the problem persists, call Customer Support.
SYSTEM ERROR: - reasonExplanation USMTP cannot deliver mail because of the specified reason (reason). The message is written to the error log. The file is set aside. The file is left on the system for examination and/or for another attempted transmission. The file name is printed in the accounting log in this format (where file is the file name):
ACC638I Mailer Daemon: File set aside: file
Read "perror Messages" in Cisco IOS for S/390 Unprefixed Messages and Codes for more information.
Recommended Action The reason directs the appropriate action.
Unknown domain literal: domain sent on RCPT TO commandExplanation SSMTP processed a RCPT TO mail command for inbound mail. The host address on the RCPT TO mail command was a domain literal. The specified domain literal (domain) is unknown to the Cisco IOS for S/390 domain name system. SSMTP accepts the RCPT TO command.
Recommended Action The Cisco IOS for S/390 administrator should decide whether or not to add a host definition for domain into the Cisco IOS for S/390 domain name system.
Mailer Daemon: File set aside: datasetExplanation USMTP cannot send the specified data set (dataset) across the TCP connection. The data set is left on the system for manual inspection. The message is written to the accounting log.
Recommended Action Examine the specified data set and this message in the error log:
ACC637I SYSTEM ERROR - reason
Where reason is an explanation of the error.
Unknown host: host sent on RCPT TO command Explanation SSMTP processed a RCPT TO mail command for inbound mail. The specified host (host) on the RCPT TO mail command is unknown to the Cisco IOS for S/390 domain name system. SSMTP accepts the RCPT TO command.
Recommended Action The Cisco IOS for S/390 administrator should decide whether or not to add a host definition for host into the Cisco IOS for S/390 domain name system.
Mailer Daemon: FILE OPEN FAILED file - reasonExplanation USMTP fails to open a mail file. The message is written to the error log. Read "perror Messages" in Cisco IOS for S/390 Unprefixed Messages and Codes for more information.
| file | The mail file. |
| reason | The reason for failing. |
Recommended Action The perror message should suggest the proper course of action.
Mailer Daemon: Sent OK; delete file fileExplanation USMTP is unsuccessful in sending the specified mail file (file). The message is written to the event log.
Mailer Daemon: Error - reasonExplanation USMTP is unable to send a file across the TCP connection or the mail data set is in error. The mail file is on disk for a later attempt at transmission. The message is written to the error log. Read "perror Messages" in Cisco IOS for S/390 Unprefixed Messages and Codes for more information.
Recommended Action The reason (reason) directs the appropriate course of action.
Mailer Daemon: File reopen failed file - reasonExplanation USMTP fails to open the specified mail file for the second time. Read "perror Messages" in Cisco IOS for S/390 Unprefixed Messages and Codes for more detailed information. The message is written to the error log.
Recommended Action The perror message should suggest the proper course of action.
Mailer Daemon: REDELIVERY FAILED (file) -- reasonExplanation USMTP fails to deliver the specified mail file for the second time. The message is written to the error log. Read "perror Messages" in Cisco IOS for S/390 Unprefixed Messages and Codes for detailed information.
Recommended Action The reason (reason) directs the appropriate course of action.
Mailer Daemon: Send file=dataset Explanation USMTP tries to use SMTP services to the specified mail data set (dataset). The message is written to the event log.
DNR indicates that Host: host has no mail support Explanation A GET HOST SERVICE BY NAME call to DNR for the specified mail host (host) returned. The results indicate that the host does not support an inbound TCP mail service at port 25. This host is dropped as a potential source to send this mail message.
Recommended Action If the host does indeed support inbound mail at TCP port 25 then the server for the network must be updated to reflect this information.
Host: host failed get service by name due to: ac.ec text, Diag=x'code' Explanation A GET HOST SERVICE BY NAME call to DNR for the specified host. Cisco IOS for S/390 attempts to send the current mail message to the host anyway.
Read "DNR Return Codes" in Cisco IOS for S/390 Unprefixed Messages and Codes for more information on action, error, and diagnostic codes.
| host | The host name. |
| ac | The action code. |
| ec | The error code. |
| message | Message text. |
| code | The diagnostic code. |
Recommended Action The error message and codes should direct a user's action.
Host: host get service by return code: rcExplanation A GET HOST SERVICE BY NAME call to DNR for the specified host failed. Module GETHBDNR was unable to accommodate the request. Cisco IOS for S/390 attempts to send the current mail message to the host anyway.
| host | The host for which the call failed. |
| rc | The error code:
-2 - Bad arguments were passed to GETHBDNR -4 - No core was available for the request -5 - A software error occurred when processing the DIRSRV call in GETHBDNR. |
Recommended Action This error could be temporary or indicative of other problems within Cisco IOS for S/390. If the problem persists, check for related SVC dumps that may have been issued. Save the T01LOG and JES log of the job. Call Customer Support.
MX record pref host dropped for route route Explanation Cisco IOS for S/390 could not use the specified host with the specified preference to deliver mail sent to the specified route. This MX record is dropped for this route. The host could be down or inaccessible, the server could indicate that the host does not support mail, etc. This is an informational message.
| pref | The preference. |
| host | The host name. |
| route | The route. |
Route: route failed get route by name due to: ac.ec text, Diag=x'code' Explanation A GET ROUTE BY NAME call to DNR for the specified route failed. Read "DNR Return Codes" in Cisco IOS for S/390 Unprefixed Messages and Codes for more information about action, error, and diagnostic codes.
Cisco IOS for S/390 attempts to send the current mail message to the route anyway.
| route | The route name. |
| ac | The action code. |
| ec | The error code. |
| message | Message text. |
| code | The diagnostic code. |
Recommended Action The error message and codes should direct a user's action.
Route: route get route by name return code: rc Explanation A GET ROUTE BY NAME call to DNR for the specified route failed. Module GETHBDNR was unable to accommodate the request. Cisco IOS for S/390 attempts to send the current mail message to the host anyway.
| route | The host for which the call failed. |
| rc | The error code:
-2 - Bad arguments were passed to GETHBDNR -4 - No core was available for the request -5 - A software error occurred when processing the DIRSRV call in GETHBDNR. |
Recommended Action This error could be temporary or indicative of other problems within Cisco IOS for S/390. If the problem persists, check for related SVC dumps that may have been issued. Save the T01LOG and JES log of the job. Call Customer Support.
Alias host:alias in X-to replaced with host_name Explanation USMTP decided that the host on the outbound X-to mail header is an alias. USMTP replaces the alias with the host name as defined by the installation in the RCPT TO SMTP command. The processing of the outbound mail continues.
Recommended Action If the specified alias is an alias for the specified host, no action is required. Otherwise, the Cisco IOS for S/390 administrator should examine the host and alias definitions to Cisco IOS for S/390.
Mailer Daemon: file dataset Sent OK to host: host/routeExplanation The outbound mailer succeeded in sending a mail data set.
Mailer Daemon: Failed (Requeue File) reason<--buff_msg Explanation USMTP tries to send a file across the TCP connection and fails. The mail file is still on disk for a later attempt at transmission. The message is written to the event log. Read "perror Messages" in Cisco IOS for S/390 Unprefixed Messages and Codes for more information.
Recommended Action The reason directs the appropriate course of action.
Explanation Mailer Daemon failed sending to host host. The file is being requeued in accordance with the UMAPTEMP parameter of the SMTP configuration statement.
| host | The HOST that failed. |
| errmsg | Detail of the error condition. |
| index | Error code. Equivalent to the error detail. |
Explanation The outbound mailer program USMTP made a call to DNR trying to resolve the subsystem name into a host name. The host name returned was longer than 255 characters. Program USMTP will exit with the x'400' ABEND for bad parameters. hhhhhhhh was the host name returned.Running H/F 4
Recommended Action Check your DNR configuration and/or domain name server configuration for your installation's MVS host name and confirm that it is 255 characters or less.
Mailer Daemon: Starting for host (alias alias) timeExplanation USMTP ptask starts on the specified host with the specified alias at the specified time. The message is written to the event log.
Mailer Daemon: ACC SMTP Sender Daemon date Directory: hlqExplanation USMTP's ptask is running. The message is written to the event log.
| date | The SMTP version date. |
| hlq | The high level qualifier for mail data sets that USMTP attempts to mail. |
Mail Host: host was not resolved by DNR, Lookup error is: ac.ec text, Diag=x'code' Explanation A GET HOST BY NAME call to DNR for a host failed. The mail host name is made of the host and domain parameters on the host statement in the DNRALCxx member. DNR could not resolve the current host name. DNR could be misconfigured or not ready to receive the DIRSRV call from the APP task group.
Read "DNR Return Codes" in Cisco IOS for S/390 Unprefixed Messages and Codes for more information on action, error, and diagnostic codes.
| host | The host name. |
| ac | The action code. |
| ec | The error code. |
| message | Message text. |
| code | The diagnostic code. |
Recommended Action The error message and codes should direct a user's action. If outbound mail is being sent by Cisco IOS for S/390 then this message can be ignored.
Mail Host: host was not resolved by DNR, Lookup error rc: rc Explanation A GET HOST BY NAME call to DNR for the specified mail host failed. Module GETHBDNR was unable to accommodate the request and returned the specified error code.
| host | The host for which the call failed. |
| rc | The error code:
-2 - Bad arguments were passed to GETHBDNR -4 - No core was available for the request -5 - A software error occurred when processing the DIRSRV call in GETHBDNR. |
Recommended Action This error could be temporary or indicative of other problems within Cisco IOS for S/390. If the problem, persists the log should be checked for dumps. The T01LOG and JES log of the job should be saved. Call Customer Support.
Explanation The current outbound mail cycle number is cccccccc. This information message only comes out when the TRACE parameter has been placed on the SMTP statement in the file APPCFGxx.
Cleaning database of dataset, data set no longer exists Explanation Cisco IOS for S/390 tries to allocate and read the specified data set (dataset). The DAIR dynamic allocation messages indicate that the data set does not exist. The Cisco IOS for S/390 mail database has this file entry removed.
Mailer Daemon: PCORE GET FAILED-Work Area Explanation Insufficient storage is available for the USMTP ptask parser work area. The pcore macro fails. The message is written to the error log. At this time, USMTP gives up trying to send this message. It tries again later when more storage is available.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and JOB logs for related messages. Check for related SVC dumps that may have been issued. Use the SNAP command to spin off a formatted snap dump of storage for the task group. If there is a lot of the same kind of storage, a ptask may be allocating storage in a loop. Retry the operation first on the current version of Cisco IOS for S/390. Retry the operation again. If it fails again, bring Cisco IOS for S/390 down and back up again. Raise the region size on the Cisco IOS for S/390 job. If the error recurs, call Customer Support.
Examining file: file for proper formatExplanation Outbound mail client USMTP reads file (file) to see if the internal format of the X-to and X-from headers are valid.
Explanation Mail file ffffffff could not be delivered to all hosts. The current outbound mail cycle number is cccccccc. A re-attempt to send mail file ffffffff will be made during cycle nnnnnnnn. This information message only comes out when the TRACE parameter has been placed on the SMTP statement in file APPCFGxx.
Mail Daemon: New file fileExplanation USMTP successfully tries to read the specified mail file (file). The message is written to the event log.
Explanation Insufficient storage is available for the USMTP ptask work area. The pcore macro fails. The message is written to the error log. At this time, USMTP gives up trying to send this message. It tries again later when more storage is available.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and JOB logs for related messages and for related SVC dumps that may have been issued. Use the SNAP command to spin off a formatted snap dump of storage for the task group. If there is a lot of the same kind of storage, a ptask may be allocating storage in a loop. Retry the operation first on the current version of Cisco IOS for S/390. Retry the operation again. If it fails again, bring Cisco IOS for S/390 down and back up again. Raise the region size on the Cisco IOS for S/390 job. If the error recurs, call Customer Support.
File: dataset has unsupported DCB attribute=type/valueExplanation DCB attributes of an outbound mail data set were examined, and a DCB attribute was found to be of an unsupported type or value. Client mail program USMTP ignores the file and it is not sent.
| dataset | The outbound mail data set. |
| attribute | The DCB attribute (either LRECL, BLOCKSIZE, RECFM, or DSORG). |
| type/value | The unsupported type or value. |
Recommended Action Examine the process that created the specified data set. Correct the process so it creates files with supported DCB attributes.
Mailer Daemon: dsn dataset is marked in error, file ignored Explanation The outbound mailer read the mail database and the specified data set (dataset) has been marked non-sendable and non-returnable by a previous mail attempt to send the file.
Recommended Action Examine the data set for bad formats. Previous mail T01LOG contains messages of the mail transfer failure. The Cisco IOS for S/390 system programmer should delete the record for this mail data set.
T01SM089IDCB for dsn=dataset recfm=r lrecl=l blksize=b dsorg=p Explanation This is an informational message that lists the DCB attributes of the specified outbound mail data set.
| dataset | The outbound mail data set.
r - The record format l - The logical record length b - The blocksize p - The data set organization |
T01SM096IFile: dataset set aside, may have ABENDed previously Explanation When client mail program USMTP was reading the mail database, it found a record indicating that the specified data set (dataset) may have previously been involved with an ABENDing USMTP. Client mail program USMTP ignores the file; it is not sent.
Recommended Action Examine the data set. Examine the current and previous runs of the Cisco IOS for S/390 product. Look for any related SVC dumps that may have been issued. Call Customer Support if an ABEND with USMTP can be found. Optionally, delete the mail database (not the data set) while the Cisco IOS for S/390 product is not running. Bring the Cisco IOS for S/390 product up; see if mail client program ABENDs and produces an SVC dump.
Explanation The outbound mailer program USMTP failed to write to the mail database mmmmmmmm. All previous cycle and count information for all mail data sets in the database will be reset to zero.
Recommended Action Examine T01LOG (the ERROR log) for related failure messages. Let those messages guide your action. Most times another address space has the mail database allocated and needs to free the database.
Explanation USMTP tries to utilize the XJES USMTP parameter for testing. The XJES parameter lets Cisco IOS for S/390 parse the headers but bypass the SMTP function and send the message output to the printer. The SYSOUT data set failed allocation due to the reason given (reason). The message is written to the error log. Read "perror Messages" in Cisco IOS for S/390 Unprefixed Messages and Codes for more information.
Recommended Action The reason determines user response.
Explanation USMTP tries to open a TCP connection to the specified host. The message is written to the error log. Read "perror Messages" in Cisco IOS for S/390 Unprefixed Messages and Codes for a detailed description.
| rc | The return code. |
| reason | The explanation of the return code. |
| host | The number of the host to which the TCP connection fails. |
| address | The IP address. |
Recommended Action The reason directs the appropriate course of action.
Mailer Daemon: (user user_name) (to host host_name) msg_textExplanation A user was rejected by the specified host.
Recommended Action The message text should direct a user's response.
MAIL SENT: time Host host by route route m lines n chars Explanation USMTP sends a mail message. The message is written to the accounting log.
| time | The time at which the message was sent. |
| host | The destination host. |
| route | The route by which the message was sent. |
| m | The length of the message in lines. |
| n | The length of the message in characters. |
Mailer Daemon: Send failed (rc=code) to Host host n by route routeExplanation USMTP tries to send mail to the specified host. The open fails. The message is written to the event log.
| code | The return code with which the open failed. |
| host | The destination host. |
| n | The host number of the destination host. |
| route | The route by which the message was sent. |
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and JOB logs for related messages. Check for any related SVC dumps that may have been issued. Get the list of commands entered by the user that generated this error.
Start a TCPEEP trace using the TELNET, DEBUG, and SYSOUT options. Retry the operation. If the error recurs, try to determine from the trace which host software is misbehaving. Call Customer Support.
Explanation USMTP sends mail from a user ID on the local host to a user ID on a remote host. The message is written to the accounting log.
| to_uid | The user ID to which the mail was sent. |
| to_host | The destination host |
| from_uid | The user ID on the local host from which the mail was sent. |
| from_host | The local host from which the mail was sent. |
UNDELIVERABLE To: to_host From: from_hostExplanation The outbound mailer failed in sending mail to a specified destination host from another host. Other messages in the T01LOG describe the nature of this failure.
T01SM112EUSMTP Mailer Daemon: File Read Error reasonExplanation USMTP tries to copy mail text to the network and fails; reason tells why Cisco IOS for S/390 cannot read the file. The message is written to the error log. Read "perror Messages" in Cisco IOS for S/390 Unprefixed Messages and Codes for more information.
Recommended Action The reason should direct your actions.
Mailer Daemon: SYSOUT alloc fail: reasonExplanation USMTP cannot deliver a message and tries to allocate another SYSOUT file for error purposes. The allocation of this new mail data set fails.
The SYSOUT data set failed allocation due to the reason given (reason). The mail message is being redirected. The message is written to the error log. Read "perror Messages" in Cisco IOS for S/390 Unprefixed Messages and Codes for more information.
Recommended Action The reason should direct your actions.
Mailer Daemon: Send failed, redeliver reasonExplanation USMTP cannot deliver mail because of the reason given (reason). The mail message is being redirected. This message is written to the accounting log.
Recommended Action Read "perror Messages" in Cisco IOS for S/390 Unprefixed Messages and Codes and take the action specified there
... Redelivery OK to: (user) tu_id m lines n chars Explanation USMTP redelivers a mail message. Mail redelivery is governed by the RETURN= parameter on the SMTP statement in APPCFGxx. This message is written to the accounting log.
| user | The user to which the mail is directed. |
| tu_id | The TSO ID of the user. |
| m | The length of the mail message in lines. |
| n | The length of the mail message in characters. |
Explanation Mailer Daemon failed in communication with host host for reason reason. Notify User user/userid of this failure.
| user | The user to be notified. |
| userid | The userid of the user to be notified. |
| host | The host that failed |
| reason | The reason the host failed. |
Explanation The FLIST parameter tells the outbound mailer how many entries to reserve for a table of IP hosts that had temporary failures during a USMTP send cycle. Once an outbound mail attempt fails with a non-permanent error to a host during a send cycle, all subsequent mail requests to the host will not be attempted and this message displays with the original reason for the temporary failure.
The FLIST feature prevents a bad mail host from backing up the outbound mail queue with a number of temporary errors.
NULL X-from: <> in outbound mail message Explanation The X-from header in the mail file contained neither a user nor host address. It was of the format: X-from: <> This is an informational message.
X-FROM User: user replaced with table entry tableExplanation USMTP processed an X-from mail header for outbound mail. Exit SMTPUSR replaced the specified user name with the specified table entry. Exit SMTPUSR lets a TSO user ID be mapped into a name. This is an informational message to keep track of a X-from user being changed by exit SMTPUSR.
Alias host:alias in X-from replaced with host_nameExplanation USMTP decided that the host on the outbound X-from mail header is an alias. USMTP replaces the alias with the host name as defined by the installation in the MAIL FROM SMTP command. The processing of the outbound mail continues.
Recommended Action None if alias is an alias for host host. If the specified alias is not supposed to be an alias for the host name, the Cisco IOS for S/390 administrator should examine the host and alias definitions to Cisco IOS for S/390.
SEND: Field = fieldExplanation The USMTP trace facility has been turned on in APPCFGxx. The X-from and X-to headers are being parsed and printed in the event log. These messages are for debugging purposes with mail. All the data found on the X-from and X-to lines are defined as Tokens and printed in subsequent messages. The field to parse is given (field). The message is written to the event log.
RCPT TO contains invalid user: user not in table Explanation SSMTP received an invalid user (user) on the RCPT TO command for inbound mail. Exit SMTPUSR rejected the user as a valid user on the system. The RCPT TO command is rejected.
Recommended Action If the user name is valid then the user must be entered in the SMTPUSR table or the SMTPUSR exit must be changed by the Cisco IOS for S/390 administrator.
|
|