Messages relating to generic M-Switch functionality
| Name | Severity | ID | Description | Action |
|---|---|---|---|---|
| AddressFailed | error | 101 | An address failed in submission | |
| AddressParse | warning | 213 | Problem found in parsing address in RFC 2822 heading field. | |
| Asn1DecodeError | error | 215 | A problem was encountered decoding an ASN.1 object. | |
| Asn1EncodeError | error | 214 | A problem was encountered encoding an ASN.1 object. | |
| Asn1PEwrite | error | 216 | A problem was encountered flattening PElements to a presentation stream. | |
| CannotChangeDir | fatal | 56 | Cannot change directory. | Check logentry for further information. Ensure that the directory exists and that the permissions are correct |
| CantBind | error | 51 | It was not possible for submit to listen on a socket for incoming connections from a client. | Check that the submit port is correctly configured. Make sure the submit program has the correct permissions |
| CantConnect2QMGR | error | 52 | It was not possible to connect to the QMGR as a passive channel | Check that QMGR is running. If it is running, there is a configuration error in the program that failed to bind that must be corrected. |
| CantCreateSocket | error | 50 | It was not possible to create a socket to connect to the submit server | Check for temporary system resource shortage. If error repeats, investigate for configuration error |
| CantSetUID | fatal | 53 | Cannot set userid mail user | Ensure that the owner of the submit program exists |
| ChangeNotification | fatal | 47 | There was a failure monitoring a folder for changes. | Check that the directory exists, and that the permissions are correct. May be a temporary system resource shortage. If error repeats, investigate for configuration error. |
| ChanProcess | notice | 150 | The channel is starting processing the given message. | |
| ChanTimeout | error | 54 | Aborting channel after timeout, for the message ID specified | The Tcl interpreter in the checking channel has timed out. Check for other errors in the logs |
| CharsetDecode | error | 209 | Cannot decode character string. | |
| CharsetEncode | error | 210 | Cannot encode character string. | |
| CharsetInit | error | 208 | Cannot initialize the character set. | |
| ContentOpen | error | 153 | Cannot open the named content file. | |
| ContentSyntaxError | fatal | 200 | The message content cannot be decoded either because of corruption, or because it is not the content type given in the message envelope. | |
| ContentTooLong | fatal | 205 | The size of the message content exceeds a limit set for the channel, MTA or user. | |
| ContentTypeNotSupported | fatal | 202 | The message cannot be transferred or delivered because the content type of the original message is not supported, or because the message cannot be converted to any content type supported by the recipient. | |
| ConversionImpractical | fatal | 203 | Some issue prevents the conversion of the message. | |
| ConversionProblem | error | 207 | There was some error converting the message content. The Switch will attempt the conversion again if the problem is not a permanent error. | |
| ConversionWithLoss | fatal | 204 | The conversion of the message would require loss of information and this has been forbidden by the sender of the message. | |
| Critical | critical | 14 | Critical 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 |
| Downgrade | error | 217 | Downgrading IPMS 88 to IPMS 84 failed. | |
| EITsNotSupported | fatal | 201 | The message cannot be processed because the message contains EITs which are not supported by the recipient. | |
| Error | error | 12 | General error used for normal errors | No Operator Action |
| 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. |
| Fatal | fatal | 13 | 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 |
| 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 |
| FieldParse | warning | 211 | Problem found in parsing RFC 2822 heading field. | |
| FilterError | error | 212 | An attempt is made to read data which is not available in this context. This is probably the result of a misconfigured list of filters. | |
| LookupFailed | error | 104 | An address failed in lookup in a remote directory. | |
| MessageDiscard | notice | 60 | A message to a recipient is being discarded. The normal reason for this is that the checking channel has been configured to discard messages which match certain characteristics. | Generally, no action is necessary. If message discard is not intended, this should be investigated for configuration error. The m-switch audit log can be inspected for more information about the message. |
| NoBilateralAgreement | fatal | 206 | The message is not allowed to be transferred to the user or the peer MTA. | |
| NoContentType | error | 152 | There is no content-type for the given message. | |
| NoRecipients | error | 103 | The message being submitted has no recipients which require processing. | |
| NoShutdownHandle | fatal | 45 | The channel failed to create a system event to mark shutdown of the service. | This would be unusual. The most likely cause would be exhaustion of system resources. If error repeats, investigate for configuration error on M-Switch or on system. |
| NoSource | error | 151 | There is no source directory for the message content for the given message. | |
| 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 |
| ProblemWithMtaOnChan | error | 55 | There was a problem with MTAs queued on a channel | iMay be problems with messages or configuration. Check other log entries for further information. Examine the message in the queue. Check the MTA configuration |
| ProcDying | fatal | 44 | The process is dying after receiving a signal from the OS | May be temporary resource problem. If error repeats, investigate for configuration error |
| Qid2Dir | error | 154 | Cannot generate the required queue name for the recipient. | |
| ReportDiscard | notice | 61 | A report to a recipient is being discarded. Reports are discarded on any error, such as routing errors or failure to transfer within the required time. | Discard of reports is often routine. Site policy may require this event to be investigated, to ensure that there is no associated message loss. The audit log can be inspected for more information about the report, and there may be indications for the failure in other event log messages. |
| RoutingTimeout | warning | 102 | The procedure to route a recipient address resulted in a network timeout. | |
| SubmitContentError | error | 105 | Various checks are made on a message content on submission. A message has failed these checks. | |
| SubmitMsgCheck | error | 100 | Various checks are made on a message on submission. A message has failed these checks. | |
| Tclerror | error | 300 | A Tcl error occurred while executing part of the checking channel. | |
| UnexpectedEvent | fatal | 46 | An unexpected event occured while waiting for the service to be shutdown. | See other log entries for further information |
| UnknownEncoding | error | 218 | In attempting to decode a message body, an unknown transfer encoding has been encountered. | |
| UUdecode | error | 301 | An error occurred extracting a uuencoded attachment. |