Message Transfer Agent Overview

The Message Transfer Agent (MTA) is responsible for:

 

Event Code: 54100

Severity Critical

Description An exception occurred in the Message Transfer Agent (MTA).

 The MTA process has terminated.

 The last function called is provided in the error label.

Impact The MTA process terminates; it is likely that messages will be lost. Users can compose and send messages but the delivery of these messages to recipient mailboxes (local or remote via networking) may be delayed until the MTA is restarted and the recovery process is completed.

Recovery Action Restart the MTA. If the MTA service does not stay up, check for database recovery and Multimedia File System (MMFS) volume corruption. If the problem persists, try rebooting the system. If this is not successful, attempt a "dummy upgrade" of the MTA components and restart the system.

Technical Support Action Check the Event Browser for related events. Look at the return code for additional information.

 

Event Code: 54101

Severity Major

Description An exception was detected by the Message Transfer Agent (MTA) but the MTA process continues.

 The last function called is provided in the error label.

Impact The MTA process continues. For example, MTA fails to open a user’s mailbox folder. Possible side-effects include delayed message delivery, message lost, non-delivery notification not generated.

Recovery Action Restart the MTA. If the MTA service does not stay up, check for database recovery and Multimedia File System (MMFS) volume corruption. If the problem persists, try rebooting the system. If this is not successful, attempt a "dummy upgrade" of the MTA components and restart the system.

Technical Support Action Check the Event Browser for related events. Look at the return code for additional information.

 

Event Code: 54102

Severity Critical

Description An error has occurred in the Message Transfer Agent (MTA).

 The MTA process has terminated.

Impact The MTA process terminates; it is likely that messages will be lost. Users can compose and send messages but the delivery of these messages to recipient mailboxes (local or remote via networking) may be delayed until the MTA is restarted and the recovery process is completed.

Recovery Action Restart the MTA. If the MTA service does not stay up, check for database recovery and Multimedia File System (MMFS) volume corruption. If the problem persists, try rebooting the system. If this is not successful, attempt a "dummy upgrade" of the MTA components and restart the system.

Technical Support Action Check the Event Browser for related events. Look at the return code for additional information.

 

Event Code: 54103

Severity Major

Description An exception was detected by the Message Transfer Agent (MTA) but the MTA process continues.

Impact The MTA process continues. For example, MTA fails to open a user’s mailbox folder. Possible side-effects include delayed message delivery, message lost, non-delivery notification not generated.

Recovery Action Restart the MTA. If the MTA service does not stay up, check for database recovery and Multimedia File System (MMFS) volume corruption. If the problem persists, try rebooting the system. If this is not successful, attempt a "dummy upgrade" of the MTA components and restart the system.

Technical Support Action Check the Event Browser for related events. Look at the return code for additional information.

 

Event Code: 54104

Severity Major

Description An exception was detected by the Message Transfer Agent (MTA) but the MTA process continues.

Impact The MTA process continues. For example, MTA fails to open a user’s mailbox folder. Possible side-effects include delayed message delivery, message lost, non-delivery notification not generated.

Recovery Action Restart the MTA. If the MTA service does not stay up, check for database recovery and Multimedia File System (MMFS) volume corruption. If the problem persists, try rebooting the system. If this is not successful, attempt a "dummy upgrade" of the MTA components and restart the system.

Technical Support Action Check the Event Browser for related events. Look at the return code for additional information.

 

Event Code: 54105

Severity Minor

Description An error occurred while retrieving the message or the sender of the message that could not be delivered. The MMFS volume might be corrupted.

Impact No non-delivery notification (NDN) is generated for this failed message delivery.

Recovery Action If this problem occurs repeatedly, contact customer support.

Technical Support Action If this problem persists, check for possible MMFS contention or corruption. For additional problem analysis, use the MTA Monitor Support tool, execute commands "trace on" followed by "no delete". Then use the Message Package Support tool to examine the messages copied into the _F1\server\UFOBox folder. When done issue the commands "trace on" followed by "undelete" from the MTA Monitor Support tool.

 Use the Message Package Support tool to delete the _F1\server\UFOBox folder.

 

Event Code: 54106

Severity Information

Description The System Manager has requested the Message Transfer Agent (MTA) to shut down.

Impact Until MTA is restarted, messages may be composed and sent but delivery to recipients is suspended.

Recovery Action Not Applicable

Technical Support Action Not Applicable

 

Event Code: 54107

Severity Minor

Description An error occurred while retrieving the message or sender of a message that could not be delivered. The MMFS volume may be corrupted.

Impact The system may not be able to generate or deliver an NDN for this message. Further events will follow in that case. The system may generate an NDN specifying that there was an error expanding the recipient list. The expanded recipient list may be empty.

Recovery Action If this problem occurs repeatedly, contact customer support.

Technical Support Action If this problem persists, check for possible MMFS contention or corruption. For additional problem analysis, use the MTA Monitor Support tool, execute commands "trace on" followed by "no delete". Then use the Message Package Support tool to examine the messages copied into the _F1\server\UFOBox folder. When done issue the commands "trace on" followed by "undelete" from the MTA Monitor Support tool.

 Use the Message Package Support tool to delete the _F1\server\UFOBox folder.

 

Event Code: 54108

Severity Information

Description The system ignores requests to generate a non-delivery notification (NDN) for system messages, a read receipt message or a broadcast message.

Impact If the class is 1, 2, or 3 there is no impact. If the class is 0, an NDN may not be generated when it should be generated.

Recovery Action Not Applicable

Technical Support Action Not Applicable

 

Event Code: 54109

Severity Minor

Description Could not generate or deliver a non-delivery notification (NDN) for a message.

Impact The original message sender will not be notified that a message previously sent could not be delivered.

Recovery Action Contact the sender of the message to inform them that their message could not be delivered. If the problem persists, check the MMFS volume or try to restart the MTA service.

Technical Support Action If this problem persists, check for possible MMFS contention or corruption. For additional problem analysis, use the MTA Monitor Support tool, execute commands "trace on" followed by "no delete". Then use the Message Package Support tool to examine the messages copied into the _F1\server\UFOBox folder. When done issue the commands "trace on" followed by "undelete" from the MTA Monitor Support tool.

 Use the Message Package Support tool to delete the _F1\server\UFOBox folder.

 

Event Code: 54110

Severity Minor

Description Attempting to generate a simpler non-delivery notification (NDN) with only the original header since a problem was encountered while attaching the entire original message to the NDN.

 The simpler NDN will eventually be generated successfully.

Impact Only the original message header will be attached instead of the whole message. The sender will not be able to resend the message and will have to record another similar message instead.

Recovery Action If the problem persists, contact customer support.

Technical Support Action Check the Event Browser for related events. Look at the return code for additional information.

 

Event Code: 54111

Severity Minor

Description An error occurred while attaching the header of the original message to the non-delivery notification (NDN).

 The header is a required element of the NDN.

Impact No NDN will be delivered to the original message sender.

Recovery Action Contact the sender of the message to inform them that their message could not be delivered.

Technical Support Action Check the Event Browser for related events. Look at the return code for additional information.

 

Event Code: 54112

Severity Debug

Description Part or all of the original message’s expanded recipient list could not be updated with the Delivery Report Done status.

Impact There is a slight risk that the NDN reporting on the same recipient is generated twice.

Recovery Action Explain to the message originator that multiple NDNs may be delivered.

Technical Support Action Look at the return code, the last function called and other events before and after this one to attempt to determine the cause. Contact customer support with all of the above information if the problem persists. If the problem recurs, there may be problems with the Address Module shared memory used by several CallPilot components.

 Use the Message Package Support tool to examine the message whose message name is given as the first parameter in the event label.

 

Event Code: 54113

Severity Minor

Description An error occurred while either reading a recipient from a message that could not be delivered or creating an address list to store one or more of those recipients.

 The non-delivery notification (NDN) will not be sent.

Impact The specific NDN for that recipient will not be generated. There may be a generic NDN generated for some other or all recipients.

Recovery Action Contact the sender of the message to inform them that their message could not be delivered. 

Technical Support Action If the problem recurs, there may be problems with the Address Module shared memory used by several CallPilot components.

 Use the Message Package Support tool to examine the message whose message name is given as the first parameter in the event label.

 

Event Code: 54114

Severity Minor

Description Delivery attempts for messages destined for the destination indicated using the AMIS protocol is temporarily suspended.

Impact The messages destined for this destination will stay in the system queue and delivery will be retried when outgoing AMIS to this destination is enabled again as indicated by another event some time later.

 It is possible that such messages become stale and non-delivery notifications generated before the delivery attempts are resumed.

Recovery Action The Administrator should check that the AMIS System Access Number (SAN) is the correct one since the call was not answered by another system that understand the AMIS-A protocol.

 Because this event may refer to one or more servers that are unreachable by the system, check the Event Browser to find out which server or servers are unreachable.

Technical Support Action Not Applicable

 

Event Code: 54115

Severity Minor

Description Delivery attempts for messages destined for the destination indicated using the AMIS protocol is temporarily suspended.

Impact The messages destined for this destination will stay in the system queue and delivery will be retried when outgoing AMIS to this destination is enabled again as indicated by another event some time later.

 It is possible that such messages become stale and non-delivery notifications generated before the delivery attempts are resumed.

Recovery Action For further information you may want to check recent events logged by the Analog Networking Agent (ANA) for the possible reasons why delivery to this destination has been temporarily disabled.

 Because this event may refer to one or more servers that are unreachable by the system, check the Event Browser to find out which server or servers are unreachable.

Technical Support Action Not Applicable

 

Event Code: 54116

Severity Information

Description Delivery attempts for messages destined for the destination indicated using the AMIS protocol is resumed.

Impact The messages destined for this destination will stay in the system queue and delivery will be retried.

 It is possible that such messages become stale and non-delivery notifications generated before the delivery attempts are resumed.

Recovery Action Not Applicable

Technical Support Action Not Applicable

 

Event Code: 54117

Severity Minor

Description Delivery attempts for messages destined for the destination indicated using the Enterprise Networking protocol is temporarily suspended.

Impact The messages destined for this destination will stay in the system queue and delivery will be retried when the Outgoing Enterprise Networking protocol to this destination is enabled again as indicated by another event some time later.

 It is possible that such messages become stale and non-delivery notifications generated before the delivery attempts are resumed.

Recovery Action For further information you may want to check recent events logged by the Analog Networking Agent (ANA) for the possible reasons why delivery to this destination has been temporarily disabled.

 Because this event may refer to one or more servers that are unreachable by the system, check the Event Browser to find out which server or servers are unreachable.

Technical Support Action Not Applicable

 

Event Code: 54118

Severity Information

Description Delivery attempts for messages destined for the destination indicated using the Enterprise Networking protocol is resumed.

Impact The messages destined for this destination will stay in the system queue and delivery will be retried.

 It is possible that such messages become stale and non-delivery notifications generated before the delivery attempts are resumed.

Recovery Action Not Applicable

Technical Support Action Not Applicable

 

Return Code: 54150

Severity Not Applicable

Description An error occurred in a local procedure call.

Impact Not Applicable

Recovery Action Not Applicable

Technical Support Action Not Applicable

 

Return Code: 54151

Severity Not Applicable

Description An invalid parameter was passed to a function.

Impact Not Applicable

Recovery Action Not Applicable

Technical Support Action Not Applicable

 

Return Code: 54152

Severity Not Applicable

Description Insufficient memory.

Impact Not Applicable

Recovery Action Not Applicable

Technical Support Action Not Applicable

 

Return Code: 54153

Severity Not Applicable

Description The Message Transfer Agent (MTA) response time was too long for the Analog Agent.

Impact Not Applicable

Recovery Action Not Applicable

Technical Support Action Not Applicable

 

Return Code: 54154

Severity Not Applicable

Description An error was returned from the object module call.

Impact Not Applicable

Recovery Action Not Applicable

Technical Support Action Not Applicable

 

Return Code: 54155

Severity Not Applicable

Description At least one Message Transfer Agent (MTA) scheduler thread for a delivery method could not be started.

 Restart the MTA.

Impact Not Applicable

Recovery Action Not Applicable

Technical Support Action Not Applicable

 

Return Code: 54156

Severity Not Applicable

Description An exception was encountered in the Message Transfer Agent (MTA).

Impact Not Applicable

Recovery Action Not Applicable

Technical Support Action Not Applicable

 

Return Code: 54157

Severity Not Applicable

Description An error was returned from the call router.

Impact Not Applicable

Recovery Action Not Applicable

Technical Support Action Not Applicable

 

Return Code: 54158

Severity Not Applicable

Description An internal system error occurred.

Impact Not Applicable

Recovery Action Not Applicable

Technical Support Action Not Applicable