Messages relating to X.400 P1 and P3
| Name | Severity | ID | Description | Action |
|---|---|---|---|---|
| Aborted | fatal | 70 | While transferring a message to a peer MTA, the association as aborted. | May be problem with network or with remote MTA. Both should be investigated |
| AssocRejected | error | 60 | It was not possible to connect to another MTA as the association was rejected | May be network problem or remote MTA not running |
| AuthNameMismatch | error | 61 | It was not possible to connect to another MTA as the authentication failed. The MTA name provided in the bind is not the expected one | Configuration error in peer MTA connection |
| AuthNullPass | error | 63 | The simple authentication check failed, as the password was NULL | Configuration error in peer MTA connection |
| AuthPassMismatch | error | 62 | It was not possible to connect to another MTA as the authentication failed. The MTA password provided in the bind is not the the expected one. | Configuration error in peer MTA connection |
| CallerLookupFailed | error | 88 | The channel was either unable to find information to identify the calling MTA, or the information supplied failed to meet the requirements. | Configuration error in peer MTA connection |
| CallingAddressError | error | 68 | The MTA is configured to require network address authentication, and the actual calling address does not match the expected calling address. | Configuration error in peer MTA connection |
| CallingAETnotValid | error | 87 | The channel is configured to require that the caller supply its Directory name in the calling application entity title (AET) and that the name be a valid name. There was a failure finding the entry corresponding to the supplied name. | Configuration error in peer MTA connection |
| CallingAETRequired | error | 86 | The channel is configured to require that the caller supply its Directory name in the calling application entity title (AET). But the caller did not supply this information. | Configuration error in peer MTA connection |
| CannotResume | error | 192 | The caller has requested association recovery, but no matching session information has been found. The channel closes the association and exits. | No operator action needed |
| DirectoryRead | error | 202 | There was a failure reading the list of files in a directory | Check that the directory exists and the permissions are correct |
| DoubleReroute | error | 67 | It is not allowed to reroute an MTA to another MTA which is itself being rerouted. | Configuration error in message routing setup |
| Error | error | 12 | General error used for normal errors | See log entry for details |
| ErrorS | error | 28 | M-Switch Error. Isode's medium term plan is to remove all common use of this event, Isode's long term plan is to remove all use of this event. | See log entry for details. |
| Ext_InternalTraceInformation_R | pdu | 32 | Read X.400 PDU | No Operator Action |
| Ext_InternalTraceInformation_W | pdu | 33 | Written X.400 PDU | No Operator Action |
| Ext_OriginatorReturnAddress_R | pdu | 34 | Read X.400 PDU | No Operator Action |
| ExtDef_ExtDefBodyPart_R | pdu | 30 | Read X.400 PDU | |
| ExtDef_ExtDefBodyPart_W | pdu | 31 | Written ROS PDU | |
| Fatal | fatal | 13 | General error used for fatal errors | See Log entry for details. Please send information on the occurrence of this event to support@isode.com |
| FatalS | fatal | 29 | Fatal M-Switch Event. This event should only occur in very unusual situations. Isode's medium term plan is to remove all use of this event | See Log entry for details. Please send information on the occurrence of this event to support@isode.com |
| FileOpen | error | 200 | There was a failure opening a file used for submission | Check that the files exists and has the correct permissions. May be a temporary resource problem. If error repeats, configuration error is likely. |
| GenericPDU | pdu | 2 | General PDU dump | No Operator Action |
| InputError | error | 204 | The input X.400 message had some formatting errors and cannot be processed | Contact operator of peer X.400 MTA to diagnose problem |
| InvalidPDU | fatal | 69 | An invalid X.400 transfer PDU was received from the peer MTA | Contact operator of peer X.400 MTA to diagnose problem |
| MHSDSinitfail | fatal | 80 | There was a failure to initialize the channel's connection to the Directory service. | Check the logs for additional information. Check that the DSA is running. |
| MHSDSopenfail | fatal | 81 | There was a failure to open the channel's connection to the Directory service. | Check the logs for additional information. The most common reason for this is incorrect credentials for the channel (bind DN and password). |
| MTA_AsymmetricTokenBody_W | pdu | 50 | Read X.400 PDU | No Operator Action |
| MTA_MessageTransferEnvelope_R | pdu | 35 | Written ROS PDU | No Operator Action |
| MTA_MessageTransferEnvelope_W | pdu | 36 | Read X.400 PDU | No Operator Action |
| MTA_MTSBindArgument_W | pdu | 37 | Written ROS PDU | No Operator Action |
| MTA_MTSBindError_R | pdu | 38 | Read X.400 PDU | No Operator Action |
| MTA_MTSBindResult_R | pdu | 39 | Written ROS PDU | No Operator Action |
| MTA_TraceInformation_W | pdu | 51 | Written X.400 PDU | No Operator Action |
| MTAnameNotFound | error | 84 | Failed to find an entry in the channel's intable for the given mTAName. | Configuration error. In EMMA, the external MTA table is the set of links visible in the X400 channel properties. These may need to be regenerated if a new MTA has been added, or if the credentials of an MTA has been changed. |
| NoBilateralAgreement | error | 85 | The channel does not have a directory-based external MTA table. It cannot use the calling mTAName to determine the caller. | Add an external MTA entry for the remote MTA |
| NoMTAParams | notice | 82 | Failed to find MTA connection information for the given MTA name, or by routing the ORaddress. | Correct Routing or MTA configuration |
| NoPAentry | error | 83 | Failed to find an entry in the channel's intable for the given calling presentation address. | Update MTA's intable |
| NoRecipientInfo | error | 203 | Could not find information to enable delivery for the given address. | Update configuration for this user |
| Notice | notice | 6 | General notice level event: See log entry for details | No Operator Action |
| NoticeS | notice | 22 | General notice level event: See log entry for details | No Operator Action |
| RdirCreate | error | 190 | Files for resumption are held in a directory. This directory could not be opened. | Check the directory exists, and has the correct permissions |
| ReadyFileWrite | error | 201 | There was a failure opening a file used to indicate submission | Check that the directory exists and the permissions are correct |
| RerouteMTA | notice | 66 | Rather than connect to the first MTA, the connection is being rerouted to the second. | No Operator Action |
| ResumeNoSlot | error | 191 | Files for resumption are held in a directory. Only a limited set of files can be created, and this limit has been reached. These files are deleted by the trash channel when they reach a certain age. If the files accumulate, this is an indication that there may be problems with communication with certain MTAs. | Investigate number of resumed files, to determine if there are problems with one or more peer MTAs and repeated failed transfers. Unwanted resume files can be deleted by hand |
| RTS84_Request_R | pdu | 40 | Read X.400 PDU | No Operator Action |
| RTS84_Request_W | pdu | 41 | Written ROS PDU | No Operator Action |
| StrongBindExpected | error | 65 | A strong bind was expected, but it was not found | |
| TrafficClass | detail | 71 | Reports the traffic class being set for the association. | Check that the value is as expected |
| Trans_Bind1988Argument_R | pdu | 42 | Read X.400 PDU | No Operator Action |
| Trans_Bind1988Argument_W | pdu | 43 | Written ROS PDU | No Operator Action |
| Trans_Bind1988Error_R | pdu | 44 | Read X.400 PDU | No Operator Action |
| Trans_Bind1988Error_W | pdu | 45 | Written ROS PDU | No Operator Action |
| Trans_Bind1988Result_R | pdu | 46 | Read X.400 PDU | No Operator Action |
| Trans_Bind1988Result_W | pdu | 47 | Written ROS PDU | No Operator Action |
| Trans_MtsAPDU_R | pdu | 48 | Read X.400 PDU | No Operator Action |
| Trans_MtsAPDU_W | pdu | 49 | Written ROS PDU | No Operator Action |
| TransferFailed | error | 64 | It was not possible to transfer a message to/from the specified MTA, and the reason is supplied. | This error should not normally occur. Problem should be reviwed with operator of peer MTA. |