Ims-ms channel error messages

MTA channels attempting to deliver to the Message Store, i.e.,   channels or   channels, can encounter several different sorts of issues:  initialization errors (errors initializing the MTA, the  Message Store,  Message Store  notify plugin code (if    named group options are set in Unified Configuration, or  the    configutil parameter is set in legacy configuration),  domain map code, or LDAP pool code) many  of which will cause the channel to abort, subsequent Message Store  errors, subsequent trouble getting LDAP information about a domain or  user, or IMAP error statuses when attempting to deliver particular  messages. When encountering a problem doing an LDAP lookup for a domain or user while attempting to deliver a message, or an IMAP error status  on a particular message, the MTA channel keeps running (and moves on to  attempting to deliver any other messages awaiting delivery).

In particular, the IMAP error statuses reported by an   channel or LMTP server, when it  attempts to access or manipulate the  Message Store, are not specific to  such  channels, but rather are general IMAP error statuses (which  may also be seen in other contexts, such as IMAP e-mail client attempts  to access or manipulate the Message Store). Additional details on the underlying Message Store issue that gave rise to an IMAP error status  may be available in the Message Store NSLOG logging for the component  which encountered the issue; in the case of the    channel or LMTP server, see the    NSLOG file discussed in  ims-ms channel  debugging and error logging.

Some IMAP error statuses are considered "permanent" errors: a message will be immediately bounced, if such an error is encountered. Other IMAP error statuses are considered "temporary" errors: a message will be retained in the MTA channel queue  (  or LMTP client   channel)  for further delivery  attempts. See IMAP error statuses for a full listing of IMAP errors, or see IMAP error statuses relvant to the MTA for the subset of IMAP errors relevant to the MTA, and in particular relevant to the  and  LMTP channels. (Note that in the case of LMTP, the IMAP error status is encountered by the LMTP server on a Message Store back end, which then reports the error to the LMTP client running on a "front end" MTA. So in the LMTP case, such errors may be reported in the LMTP server&#x27;s message transaction log file, in an  LMTP server log file, and also as a reported LMTP error in the  LMTP client&#x27;s log file or in the  message transaction log file  of the "front end" MTA running the LMTP client channel.)

 +The IMAP error text is localizable. The text shown in this table is merely the default text (which happens to be English).

 ++For completeness, additional IMAP statuses are listed, though they  are not normally relevant (do not normally appear) as    channel or  LMTP channel  delivery error statuses.

The IMAP delivery temporary error statuses listed in IMAP error statuses relevant to the MTA may  appear in the "history" field of messages that failed a  delivery attempt; this is visible via, for instance, the    command of the   utility, as  well as being physically present in the history field in the deferred  message files awaiting further delivery attempts in the MTA    channel  disk queue area or   channel disk queue area. (Should a message eventually bounce due to "timing out", such history information may also be included  in the bounce message, as controlled by the    MTA option.)  Furthermore, the temporary error text will be included in the     channel&#x27;s  " " record  in the MTA message transaction log file, should such  logging be enabled via use of the    channel option.

The IMAP delivery permanent error statuses shown in IMAP error statuses will  appear in the   channel&#x27;s or   channel&#x27;s  " " or  " " record in  the MTA message transaction log file, should such logging be enabled via use of the    channel option.

As with other types of channel processes, the  channel  processes  do not have an infinite life time: after running for a (configurable)  while, they shut down (and the Job Controller  will start up new    channel processes, as needed). The Job Controller options    and   (  and ,  respectively, in legacy configuration) and the   channel&#x27;s own 60 seconds limit on  time to persist while idle, control the timing of the    channel  process "recycling". In addition, an administrator   of  the Job Controller will cause the Job Controller to tell channel  processes to shut down. So notices in the  log file  such as the following are part of normal operation:

At Notice level: product ims_master version shutting down product ims_master version starting up And at Debug level: When the  channel process&#x27; threads have all  been idle for 60 seconds or more (or are deadlocked): idle shutdown When a thread is exiting due to having no work to do: Tthread-number exiting When the Job Controller is telling a process to shut down due to the process having gotten old: EOF from job controller And after an administrator   of the Job Controller, the following  sorts of messages can also be expected in the   file. At Debug level: shutdown received When the Job Controller is telling a process to shut down due to an administrator   command: exit from job controller mta-status A message (at Warning level) of Shutdown timeout, possible deadlock however, is an indication that one or more threads in a process attempting to shut down have not been able to finish their work. If this error repeats, it may indicate that a mailbox is corrupted or  locked.

In an MTA message transaction log file " " or  " " record, a reason  of " " indicates that a delivery  attempt for that recipient is being deferred due to a shutdown in  progress---either an administrator&#x27;s manual shutdown, or a shutdown due  to a channel process "timing out".

See also:
 * ims-ms channels
 * LMTP channels
 * LMTP client TCPIP channels
 * The Message Store
 * notifytarget options
 * IMAP error statuses
 * lmtp Option
 * smtp Option
 * limitheadertermination Option
 * quotagraceperiod Store Option
 * Sieve fileinto action
 * MTA transaction log entry format
 * logging Option
 * log_reason MTA Option
 * Job Controller
 * backoff Option
 * defaultpartition Store Option
 * checkdiskusage Store Option
 * diskusagethreshold Store Option
 * history_to_return MTA Option
 * ims-ms channel debugging and error logging