Isode Events (Facility Detail)

Summary: Isode components write to logging streams when events occur.

Facility MTA_X400

Messages relating to X.400 P1 and P3

NameSeverityIDDescriptionAction
Abortedfatal70While transferring a message to a peer MTA, the association as aborted. May be problem with network or with remote MTA. Both should be investigated
AssocRejectederror60 It was not possible to connect to another MTA as the association was rejected May be network problem or remote MTA not running
Authenticationerror101Remote MTA/MS rejected the credentials of the calling system. Check the credentials which are being sent.
AuthNameMismatcherror61 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
AuthNullPasserror63The simple authentication check failed, as the password was NULL Configuration error in peer MTA connection
AuthPassMismatcherror62It 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
BadContexterror115The initiator passed a set of presentation contexts which was invalid.
BadCredentialserror107The remote MTA did not send acceptable credentials. This is either a local configuration issue, or a compatibility issue.
Busyerror100Remote MTA or MS is busy. Connection can be attempt again later.
CallerLookupFailederror88The 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
CallingAddressErrorerror68The 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
CallingAETnotValiderror87The 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
CallingAETRequirederror86The 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
CannotResumeerror192The caller has requested association recovery, but no matching session information has been found. The channel closes the association and exits. No operator action needed
Connectinginfo72A new connection is being opened to a peer MTA Check that the values are as expected
DecodeErrorerror90There was a problem decoding some data item. Check for more detailed logging of the problem.
DeliveryErrorerror149The delivery of the message or report failed.
DirectoryReaderror202There was a failure reading the list of files in a directory Check that the directory exists and the permissions are correct
DiscardRetContentwarning208There is no content type so the returned-content in the report is discarded.
DoubleRerouteerror67It is not allowed to reroute an MTA to another MTA which is itself being rerouted. Configuration error in message routing setup
EncodeErrorerror89There was a problem encoding some data item. Check for more detailed logging of the problem.
Errorerror12General error used for normal errors See log entry for details
ErrorSerror28M-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_Rpdu32Read X.400 PDUNo Operator Action
Ext_InternalTraceInformation_Wpdu33Written X.400 PDUNo Operator Action
Ext_OriginatorReturnAddress_Rpdu34Read X.400 PDUNo Operator Action
ExtDef_ExtDefBodyPart_Rpdu30Read X.400 PDU
ExtDef_ExtDefBodyPart_Wpdu31Written ROS PDU
Fatalfatal13General error used for fatal errors See Log entry for details. Please send information on the occurrence of this event to support@isode.com
FatalSfatal29 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
FileOpenerror200There 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.
GenericPDUpdu2General PDU dump No Operator Action
InputErrorerror204The input X.400 message had some formatting errors and cannot be processed Contact operator of peer X.400 MTA to diagnose problem
InternalErrorerror110There is an internal problem with the configuration or the operation of the channel. Check the channel's configuration
InvalidAddresserror92The address for the remote MTA is invalid. Check the configuration of the channel for the remote MTA.
InvalidORaddresserror144The given UA address is invalid.
InvalidPDUfatal69An invalid X.400 transfer PDU was received from the peer MTA Contact operator of peer X.400 MTA to diagnose problem
Listeningnotice206P1 stand-alone listener
MHSDSinitfailfatal140There 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.
MHSDSopenfailfatal141There 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_Wpdu50Read X.400 PDUNo Operator Action
MTA_MessageTransferEnvelope_Rpdu35Written ROS PDUNo Operator Action
MTA_MessageTransferEnvelope_Wpdu36Read X.400 PDUNo Operator Action
MTA_MTSBindArgument_Wpdu37Written ROS PDUNo Operator Action
MTA_MTSBindError_Rpdu38Read X.400 PDUNo Operator Action
MTA_MTSBindResult_Rpdu39Written ROS PDUNo Operator Action
MTA_TraceInformation_Wpdu51Written X.400 PDUNo Operator Action
MTAnameNotFounderror84Failed 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.
NoAddresserror91There was no address for the remote MTA. Check the configuration of the channel for the remote MTA.
NoBilateralAgreementerror85The 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
NoChannelInfoerror146Cannot find the information for the channel. address. Check the configuration for the channel
NoMSaddresserror147Cannot find the presentation address to call. Check the configuration for the message store
NoMSservererror148Cannot find the presentation address to call. Check the configuration for the message store
NoMTAParamsnotice82Failed to find MTA connection information for the given MTA name, or by routing the ORaddress. Correct Routing or MTA configuration
NoPAentryerror83Failed to find an entry in the channel's intable for the given calling presentation address. Update MTA's intable
NoRecipientInfoerror203Could not find information to enable delivery for the given address. Update configuration for this user
NoStoreInfoerror145Cannot find the message store information for the given address. Check the configuration of the user with the address
Noticenotice6 General notice level event: See log entry for details No Operator Action
NoticeSnotice22General notice level event: See log entry for details No Operator Action
P1APDUconnectnotice302A connection is received. No Operator Action
P1APDUdisconnectnotice303Disconnected. No Operator Action
P1APDUerrorerror301General error used for normal errors No Operator Action
P1APDUnoticenotice300General notice level event: See log entry for details No Operator Action
P3connectnotice311Connecting to the given message store.
P3ConnectFailerror143The P3 channel failed to connect to the UA/MS. Action depends upon the detailed reason for the problem.
P3ConnectOKnotice142The P3 channel has connected successfully to the UA/MS.
P3redirectnotice310The message store is redirected to another message store.
P3senderrornotice312Sending error to client.
RdirCreateerror190Files for resumption are held in a directory. This directory could not be opened. Check the directory exists, and has the correct permissions
ReadyFileWriteerror201There was a failure opening a file used to indicate submission Check that the directory exists and the permissions are correct
ReleaseRejectederror111The local MTA attempted to release the association, but this release was rejected by the peer MTA. The local MTA aborts the association.
RerouteMTAnotice66Rather than connect to the first MTA, the connection is being rerouted to the second. No Operator Action
ResumeNoSloterror191Files 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
Resuminginfo207Records starting offset for resumption
RTS84_Request_Rpdu40Read X.400 PDUNo Operator Action
RTS84_Request_Wpdu41Written ROS PDUNo Operator Action
RTSAborterror112When performing an RTS operation, an abort was encountered.
RTSRecovererror106Remote MTA was not able to recover the association. The local MTA will attempt again without attempting recovery. Do not attempt to recover the association.
RTSRejecterror105Remote MTA has rejected the connection. Ask the remote MTA administrator for details.
SecurityContexterror103Remote MTA/MS rejected the security of the calling system. Check the security context which is being sent.
StrongAuthFailederror108The remote MTA's strong bind failed. This could be because of a problem with the credentials, or a problem with the local configuration used to check the credentials. Check the local strong auth trust anchors
StrongAuthProblemerror109There is a local problem with strong authentication. Check the strong authentication configuration
StrongBindExpectederror65A strong bind was expected, but it was not found
TrafficClassdetail71Reports the traffic class being set for the association. Check that the value is as expected
Trans_Bind1988Argument_Rpdu42Read X.400 PDUNo Operator Action
Trans_Bind1988Argument_Wpdu43Written ROS PDUNo Operator Action
Trans_Bind1988Error_Rpdu44Read X.400 PDUNo Operator Action
Trans_Bind1988Error_Wpdu45Written ROS PDUNo Operator Action
Trans_Bind1988Result_Rpdu46Read X.400 PDUNo Operator Action
Trans_Bind1988Result_Wpdu47Written ROS PDUNo Operator Action
Trans_MtsAPDU_Rpdu48Read X.400 PDUNo Operator Action
Trans_MtsAPDU_Wpdu49Written ROS PDUNo Operator Action
TransferCompletewarning113The RTS transfer of a message was already completed.
TransferDiscarderror114The RTS transfer of a message has been discarded as a result of too many attempts following RTS transfer discard or interrupt. The MTA will attempt the transfer later.
TransferFailederror64It 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.
TransientErrorerror205A temporary error was encountered when decoding the ASN.1 for an inbound message. The problem can clear later. Check that the problem is not repeating
UnacceptableModeerror102The remote MTA rejects the proposed dialogue mode. Change the configuration to propose a different mode.
UpperBoundExceedederror93The given field has been configured with a value whose length exceeds the permitted upper bound for this item. Check the configuration of the item in question.
ValidationFailureerror104The remote MTA sent an RTS validation error. The local MTA may not be registered with the remote MTA.

GenericPDU

Message Text
  • %1
Parameters
  1. Name of file containing PDU
Description
General PDU dump
Action
No Operator Action

Notice

Message Text
  • %1
Parameters
  1. Text describing condition
Description
General notice level event: See log entry for details
Action
No Operator Action

Error

Message Text
  • %1
Parameters
  1. Text describing error
Description
General error used for normal errors
Action
See log entry for details

Fatal

Message Text
  • %1
Parameters
  1. Text describing error
Description
General error used for fatal errors
Action
See Log entry for details. Please send information on the occurrence of this event to support@isode.com

NoticeS

Message Text
  • %1 %2
Parameters
  1. Text describing condition
  2. Additional text field
Description
General notice level event: See log entry for details
Action
No Operator Action

ErrorS

Message Text
  • %1 %2
Parameters
  1. Text describing error
  2. Additional text field
Description
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.
Action
See log entry for details.

FatalS

Message Text
  • %1 %2
Parameters
  1. Text describing error
  2. Additional text field
Description
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
Action
See Log entry for details. Please send information on the occurrence of this event to support@isode.com

ExtDef_ExtDefBodyPart_R

Message Text
  • %1
Parameters
  1. File containing PDU
Description
Read X.400 PDU
Action

ExtDef_ExtDefBodyPart_W

Message Text
  • %1
Parameters
  1. File containing PDU
Description
Written ROS PDU
Action

Ext_InternalTraceInformation_R

Message Text
  • %1
Parameters
  1. File containing PDU
Description
Read X.400 PDU
Action
No Operator Action

Ext_InternalTraceInformation_W

Message Text
  • %1
Parameters
  1. File containing PDU
Description
Written X.400 PDU
Action
No Operator Action

Ext_OriginatorReturnAddress_R

Message Text
  • %1
Parameters
  1. File containing PDU
Description
Read X.400 PDU
Action
No Operator Action

MTA_MessageTransferEnvelope_R

Message Text
  • %1
Parameters
  1. File containing PDU
Description
Written ROS PDU
Action
No Operator Action

MTA_MessageTransferEnvelope_W

Message Text
  • %1
Parameters
  1. File containing PDU
Description
Read X.400 PDU
Action
No Operator Action

MTA_MTSBindArgument_W

Message Text
  • %1
Parameters
  1. File containing PDU
Description
Written ROS PDU
Action
No Operator Action

MTA_MTSBindError_R

Message Text
  • %1
Parameters
  1. File containing PDU
Description
Read X.400 PDU
Action
No Operator Action

MTA_MTSBindResult_R

Message Text
  • %1
Parameters
  1. File containing PDU
Description
Written ROS PDU
Action
No Operator Action

RTS84_Request_R

Message Text
  • %1
Parameters
  1. File containing PDU
Description
Read X.400 PDU
Action
No Operator Action

RTS84_Request_W

Message Text
  • %1
Parameters
  1. File containing PDU
Description
Written ROS PDU
Action
No Operator Action

Trans_Bind1988Argument_R

Message Text
  • %1
Parameters
  1. File containing PDU
Description
Read X.400 PDU
Action
No Operator Action

Trans_Bind1988Argument_W

Message Text
  • %1
Parameters
  1. File containing PDU
Description
Written ROS PDU
Action
No Operator Action

Trans_Bind1988Error_R

Message Text
  • %1
Parameters
  1. File containing PDU
Description
Read X.400 PDU
Action
No Operator Action

Trans_Bind1988Error_W

Message Text
  • %1
Parameters
  1. File containing PDU
Description
Written ROS PDU
Action
No Operator Action

Trans_Bind1988Result_R

Message Text
  • %1
Parameters
  1. File containing PDU
Description
Read X.400 PDU
Action
No Operator Action

Trans_Bind1988Result_W

Message Text
  • %1
Parameters
  1. File containing PDU
Description
Written ROS PDU
Action
No Operator Action

Trans_MtsAPDU_R

Message Text
  • %1
Parameters
  1. File containing PDU
Description
Read X.400 PDU
Action
No Operator Action

Trans_MtsAPDU_W

Message Text
  • %1
Parameters
  1. File containing PDU
Description
Written ROS PDU
Action
No Operator Action

MTA_AsymmetricTokenBody_W

Message Text
  • %1
Parameters
  1. File containing PDU
Description
Read X.400 PDU
Action
No Operator Action

MTA_TraceInformation_W

Message Text
  • %1
Parameters
  1. File containing PDU
Description
Written X.400 PDU
Action
No Operator Action

AssocRejected

Message Text
  • Association Rejected to MTA %1, %2
Parameters
  1. Peer MTA to which the association was rejected
  2. Text describing error
Description
It was not possible to connect to another MTA as the association was rejected
Action
May be network problem or remote MTA not running

AuthNameMismatch

Message Text
  • Authorization failed, MTA name mismatch, expected '%1' but got '%2'
Parameters
  1. The expected value of MTA name in the Bind
  2. The value of MTA name received in the Bind
Description
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
Action
Configuration error in peer MTA connection

AuthPassMismatch

Message Text
  • Authorization failed for %1, password mismatch, expected '%2' but got '%3'
Parameters
  1. Peer MTA name
  2. The expected value of MTA password in the Bind
  3. The value of MTA password received in the Bind
Description
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.
Action
Configuration error in peer MTA connection

AuthNullPass

Message Text
  • Authorization failed for MTA %1, as the MTA password was NULL
Parameters
  1. Peer MTA name
Description
The simple authentication check failed, as the password was NULL
Action
Configuration error in peer MTA connection

TransferFailed

Message Text
  • Transfer to MTA %1 failed: %2
Parameters
  1. Peer MTA name
  2. Failure reason
Description
It was not possible to transfer a message to/from the specified MTA, and the reason is supplied.
Action
This error should not normally occur. Problem should be reviwed with operator of peer MTA.

StrongBindExpected

Message Text
  • strong bind expected, but not found
Description
A strong bind was expected, but it was not found
Action

RerouteMTA

Message Text
  • Rerouting MTA %1 to MTA %2
Parameters
  1. MTA name being rerouted
  2. Target MTA name
Description
Rather than connect to the first MTA, the connection is being rerouted to the second.
Action
No Operator Action

DoubleReroute

Message Text
  • Rerouting MTA %1 to MTA which is rerouted
Parameters
  1. MTA name
Description
It is not allowed to reroute an MTA to another MTA which is itself being rerouted.
Action
Configuration error in message routing setup

CallingAddressError

Message Text
  • Authorization failed for MTA %1, calling address mismatch, %2 != %3
Parameters
  1. Peer MTA name
  2. Expected calling address
  3. Actual calling address
Description
The MTA is configured to require network address authentication, and the actual calling address does not match the expected calling address.
Action
Configuration error in peer MTA connection

InvalidPDU

Message Text
  • Invalid PDU received from MTA %1: %2
Parameters
  1. Peer MTA name
  2. Additional information
Description
An invalid X.400 transfer PDU was received from the peer MTA
Action
Contact operator of peer X.400 MTA to diagnose problem

Aborted

Message Text
  • Association with MTA %1 while transferring %2, reason=%3
Parameters
  1. Peer MTA name
  2. P1 message ID
  3. Reason for failure
Description
While transferring a message to a peer MTA, the association as aborted.
Action
May be problem with network or with remote MTA. Both should be investigated

TrafficClass

Message Text
  • Traffic class set to %1 for %2
Parameters
  1. The decimal traffic class value
  2. Initiator or responder
Description
Reports the traffic class being set for the association.
Action
Check that the value is as expected

Connecting

Message Text
  • Connecting%1 (RTS %2 mode, %3) to site %4
Parameters
  1. Indicates if recovery is in use
  2. RTS mode, 1988 normal or 1984 mode connection
  3. TWA or Monologue mode
  4. Internal name of peer MTA
Description
A new connection is being opened to a peer MTA
Action
Check that the values are as expected

NoMTAParams

Message Text
  • Cannot find MTA information for %1 (or address %2)
Parameters
  1. MTA name
Description
Failed to find MTA connection information for the given MTA name, or by routing the ORaddress.
Action
Correct Routing or MTA configuration

NoPAentry

Message Text
  • Cannot locate entry in table %1 for address %2 (key:%3)
Parameters
  1. Name of table
  2. Calling presentation address using macros
  3. Calling presentation address without macros. This is the key used.
Description
Failed to find an entry in the channel's intable for the given calling presentation address.
Action
Update MTA's intable

MTAnameNotFound

Message Text
  • Cannot find entry in external MTA table for mTAName %1
Parameters
  1. mTAName from incoming X.400 bind operation
Description
Failed to find an entry in the channel's intable for the given mTAName.
Action
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

Message Text
  • No bilateral agreement found for caller %1
Parameters
  1. Directory name of the MTA's entry for which a bilateral agreement was expected.
Description
The channel does not have a directory-based external MTA table. It cannot use the calling mTAName to determine the caller.
Action
Add an external MTA entry for the remote MTA

CallingAETRequired

Message Text
  • The caller did not supply its name in the calling AET
Description
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.
Action
Configuration error in peer MTA connection

CallingAETnotValid

Message Text
  • Cannot find entry corresponding to AET %1
Parameters
  1. Directory name within the calling AET.
Description
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.
Action
Configuration error in peer MTA connection

CallerLookupFailed

Message Text
  • Failure finding information for calling MTA name=%1 address=%2
Parameters
  1. mTAName supplied in bind
  2. calling presentation address
Description
The channel was either unable to find information to identify the calling MTA, or the information supplied failed to meet the requirements.
Action
Configuration error in peer MTA connection

EncodeError

Message Text
  • Failed to encode %1
Parameters
  1. item for which the encode failed
Description
There was a problem encoding some data item.
Action
Check for more detailed logging of the problem.

DecodeError

Message Text
  • Failed to decode %1, %2
Parameters
  1. item for which the encode failed
  2. detail for the error
Description
There was a problem decoding some data item.
Action
Check for more detailed logging of the problem.

NoAddress

Message Text
  • No address for %1
Parameters
  1. The name of the MTA being attempted
Description
There was no address for the remote MTA.
Action
Check the configuration of the channel for the remote MTA.

InvalidAddress

Message Text
  • The address '%1' for %2
Parameters
  1. The string form of the address.
  2. The name of the MTA being attempted or the local calling address
Description
The address for the remote MTA is invalid.
Action
Check the configuration of the channel for the remote MTA.

UpperBoundExceeded

Message Text
  • The field %1 with value %2 exceeds its upper bound of %3 characters
Parameters
  1. The name of the field
  2. The configured value of the field
  3. The permitted maximum length of this field
Description
The given field has been configured with a value whose length exceeds the permitted upper bound for this item.
Action
Check the configuration of the item in question.

Busy

Message Text
  • MTA/MS busy
Description
Remote MTA or MS is busy.
Action
Connection can be attempt again later.

Authentication

Message Text
  • Credentials rejected
Description
Remote MTA/MS rejected the credentials of the calling system.
Action
Check the credentials which are being sent.

UnacceptableMode

Message Text
  • Dialog mode unacceptable %1
Parameters
  1. The dialog mode proposed
Description
The remote MTA rejects the proposed dialogue mode.
Action
Change the configuration to propose a different mode.

SecurityContext

Message Text
  • The proposed security context was rejected
Description
Remote MTA/MS rejected the security of the calling system.
Action
Check the security context which is being sent.

ValidationFailure

Message Text
  • Remote MTA failed to validate local MTA
Description
The remote MTA sent an RTS validation error.
Action
The local MTA may not be registered with the remote MTA.

RTSReject

Message Text
  • MTA rejects connection
Description
Remote MTA has rejected the connection.
Action
Ask the remote MTA administrator for details.

RTSRecover

Message Text
  • MTA failed to recover
Description
Remote MTA was not able to recover the association. The local MTA will attempt again without attempting recovery.
Action
Do not attempt to recover the association.

BadCredentials

Message Text
  • Remote MTA sent invalid credentials, %1
Parameters
  1. The detailed reason for the rejection
Description
The remote MTA did not send acceptable credentials.
Action
This is either a local configuration issue, or a compatibility issue.

StrongAuthFailed

Message Text
  • Strong Authentication failure, %1
Parameters
  1. The detailed reason for the rejection
Description
The remote MTA's strong bind failed. This could be because of a problem with the credentials, or a problem with the local configuration used to check the credentials.
Action
Check the local strong auth trust anchors

StrongAuthProblem

Message Text
  • Local Strong Authentication problem, %1
Parameters
  1. The detailed reason for the problem
Description
There is a local problem with strong authentication.
Action
Check the strong authentication configuration

InternalError

Message Text
  • Internal error, %1
Parameters
  1. The detailed reason for the rejection
Description
There is an internal problem with the configuration or the operation of the channel.
Action
Check the channel's configuration

ReleaseRejected

Message Text
  • Release rejected by peer, %1
Parameters
  1. The detailed reason for the rejection
Description
The local MTA attempted to release the association, but this release was rejected by the peer MTA. The local MTA aborts the association.
Action

RTSAbort

Message Text
  • RTS abort %1 [%2]
Parameters
  1. The operation in progress when the abort occurred.
  2. Detail for the abort.
Description
When performing an RTS operation, an abort was encountered.
Action

TransferComplete

Message Text
  • Transfer of %1 to %2 already complete
Parameters
  1. The MPDUid of the message
  2. The peer to which the message was being transferred.
Description
The RTS transfer of a message was already completed.
Action

TransferDiscard

Message Text
  • Transfer of %1 to %2 discarded
Parameters
  1. The MPDUid of the message
  2. The peer to which the message was being transferred.
Description
The RTS transfer of a message has been discarded as a result of too many attempts following RTS transfer discard or interrupt. The MTA will attempt the transfer later.
Action

BadContext

Message Text
  • Invalid Presentation Context
Description
The initiator passed a set of presentation contexts which was invalid.
Action

MHSDSinitfail

Message Text
  • Failed to initialize directory connection
Description
There was a failure to initialize the channel's connection to the Directory service.
Action
Check the logs for additional information. Check that the DSA is running.

MHSDSopenfail

Message Text
  • Failed to open directory connection
Description
There was a failure to open the channel's connection to the Directory service.
Action
Check the logs for additional information. The most common reason for this is incorrect credentials for the channel (bind DN and password).

P3ConnectOK

Message Text
  • P3 connected to %1
Parameters
  1. The name of the UA/MS
Description
The P3 channel has connected successfully to the UA/MS.
Action

P3ConnectFail

Message Text
  • P3 failed to connect to %1
Parameters
  1. The name of the UA/MS
Description
The P3 channel failed to connect to the UA/MS.
Action
Action depends upon the detailed reason for the problem.

InvalidORaddress

Message Text
  • Invalid OR-address %1
Parameters
  1. The incorrect address
Description
The given UA address is invalid.
Action

NoStoreInfo

Message Text
  • Failed to get MessageStore for %1
Parameters
  1. The address being used
Description
Cannot find the message store information for the given address.
Action
Check the configuration of the user with the address

NoChannelInfo

Message Text
  • Failed to get channel info for %1
Parameters
  1. The DN of the channel being used.
Description
Cannot find the information for the channel. address.
Action
Check the configuration for the channel

NoMSaddress

Message Text
  • Failed to get message store address for %1
Parameters
  1. The DN of the shared message store.
Description
Cannot find the presentation address to call.
Action
Check the configuration for the message store

NoMSserver

Message Text
  • Failed to get message store server for %1
Parameters
  1. The DN of the shared message store.
Description
Cannot find the presentation address to call.
Action
Check the configuration for the message store

DeliveryError

Message Text
  • Error delivering %1, %2
Parameters
  1. The type of object being delivered (message or report)
  2. Detail for the error
Description
The delivery of the message or report failed.
Action

RdirCreate

Message Text
  • Failed to resumption directory %1
Parameters
  1. name of directory
Description
Files for resumption are held in a directory. This directory could not be opened.
Action
Check the directory exists, and has the correct permissions

ResumeNoSlot

Message Text
  • No slots available in resumption directory %1
Parameters
  1. name of directory
Description
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.
Action
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

CannotResume

Message Text
  • Cannot recover association from caller %1
Parameters
  1. The caller's presentation address
Description
The caller has requested association recovery, but no matching session information has been found. The channel closes the association and exits.
Action
No operator action needed

FileOpen

Message Text
  • Failed to open submission file %1
Parameters
  1. name of file
Description
There was a failure opening a file used for submission
Action
Check that the files exists and has the correct permissions. May be a temporary resource problem. If error repeats, configuration error is likely.

ReadyFileWrite

Message Text
  • Failed to create file %1 in %2
Parameters
  1. name of file
  2. directory for ready file
Description
There was a failure opening a file used to indicate submission
Action
Check that the directory exists and the permissions are correct

DirectoryRead

Message Text
  • Failed to read directory %1
Parameters
  1. name of directory
Description
There was a failure reading the list of files in a directory
Action
Check that the directory exists and the permissions are correct

NoRecipientInfo

Message Text
  • Failed to get information for address %1
Parameters
  1. ORaddress of recipient
Description
Could not find information to enable delivery for the given address.
Action
Update configuration for this user

InputError

Message Text
  • Input message error: %1 (%2) '%3'
Parameters
  1. Error type
  2. Numeric error number
  3. Value giving the error
Description
The input X.400 message had some formatting errors and cannot be processed
Action
Contact operator of peer X.400 MTA to diagnose problem

TransientError

Message Text
  • Transient error with ASN.1
Description
A temporary error was encountered when decoding the ASN.1 for an inbound message. The problem can clear later.
Action
Check that the problem is not repeating

Listening

Message Text
  • Listening on %1
Parameters
  1. Presentation address for listen
Description
P1 stand-alone listener
Action

Resuming

Message Text
  • Resumption starts at %1 bytes
Parameters
  1. Offset of start of resumption
Description
Records starting offset for resumption
Action

DiscardRetContent

Message Text
  • Discarding returned content of report %1
Parameters
  1. queue id of report
Description
There is no content type so the returned-content in the report is discarded.
Action

P1APDUnotice

Message Text
  • %1
Parameters
  1. Text describing condition
Description
General notice level event: See log entry for details
Action
No Operator Action

P1APDUerror

Message Text
  • %1
Parameters
  1. Text describing error
Description
General error used for normal errors
Action
No Operator Action

P1APDUconnect

Message Text
  • Connection %1 for %2
Parameters
  1. port status
  2. connection data
Description
A connection is received.
Action
No Operator Action

P1APDUdisconnect

Message Text
  • Connection disconnect
Description
Disconnected.
Action
No Operator Action

P3redirect

Message Text
  • Message store %1 redirected to %2
Parameters
  1. original MS
  2. target MS
Description
The message store is redirected to another message store.
Action

P3connect

Message Text
  • Connecting to %1
Parameters
  1. OR-address of target MS
Description
Connecting to the given message store.
Action

P3senderror

Message Text
  • (%1) sending %2 error
Parameters
  1. FD of association
  2. Name of error returned
Description
Sending error to client.
Action

All rights reserved © 2002 - 2024 Isode Ltd.