Test -rewrite utility

Test address rewriting specified by an MTA configuration; test syntactic validity of an MTA configuration.

Syntax
imsimta test -rewrite &#x5b;test-address&#x5d;

Restrictions
Must be superuser or the MTA user (the  option in  , or prior to MS 7.0.5, the    MTA  Tailor option value), or be in the group specified by the    option in   (prior to MS  7.0.5, be in the    group), in order to display   ,  , or    output.

Optional parameter specifying one or more (comma-separated) addresses to rewrite.

Description
provides a straightforward test facility for examining the MTA&#x27;s address rewriting and channel matching  process without actually sending any message. Various switches can be used to control whether   uses the  configuration text files or the compiled configuration (if present),  the amount of output produced, and so on.

The  utility has several especially  common and useful uses:



 testing overall syntactic validity (though not   semantic correctness) of the MTA configuration, 

 testing MTA configuration changes prior to making them   "live" with    , and conversely    checking that the compiled configuration in fact corresponds to the    "most current" versions of the configuration files, 

 testing that the Messaging Server LDAP configuration information   is accessible, 

 testing that the LDAP server is responding to domain and   user/group lookups, 

 testing the rewriting,   alias lookup and expansion, and resulting    routing, of specific addresses, 

 testing the expansion (membership) of    groups and mailing lists, 

 testing the canonicalization of specific (local) addresses resulting  from address reversal (i.e.,    testing how local   addresses will appear in header lines), 

 testing the effects of     address-based    mapping tables, </li>

 testing the effects of posting restrictions such as restrictions   on mailing list postings, </li>

 determining which Sieve filters   are applicable for a particular    recipient address, </li>

 testing SRS/MUL encoding and decoding of addresses (if   SRS MTA options have been configured). </li>

</ol>

If a test address is specified on the command line,  applies MTA address rewriting to that address, reports  the results, and exits. If no test address is specified,  will enter a loop, prompting for an address,  rewriting it, and prompting again for another address. will exit when CTRL/D (UNIX)   is  entered.

In interactive mode, note that the caret character,, may  be used to enter a character or characters by ASCII value (in  hexadecimal); each character must be entered as a two digit hexadecimal  value, with a final caret character meaning to return to  "normal" (as typed) character entry. For instance,   is one way of entering a space character. To enter a literal caret character, caret-quote the caret,.

When testing an alias corresponding to a mailing list which has an    or    type of named parameter (legacy configuration) or an   or   alias option (Unified Configuration)  controlling who may post to the  list, or which has an    LDAP  attribute  controlling who may post to the list, or when testing rewriting when     or related mapping tables are in effect, note that by  default   uses as the posting address  the return address of the  local postmaster as specified by the     MTA option. To specify a different posting address for the rewriting process, use the   switch.

Note that as mentioned above, the   utility also provides a basic "sanity check" of the  syntactical correctness (though not the semantic correctness) of the  configuration. In particular, if the utility returns any Error in mm_init -- detail error message, that is a warning of a serious configuration problem, preventing the MTA from operating.

If an active compiled configuration appears to be "out-of-date" compared to configuration files, then the    utility will issue the following  warning (but proceed to operate): Warning - compiled configuration does not match configuration files -- detail with further detail (such as what file(s) appear to have been modified subsequent to the compilation of the currently active compiled  configuration) in the   text.

The  utility also provides a way of  checking that the LDAP server is responsive. Using the   switch, that is, using an   command, is a way of checking that the  Messaging Server configuration information in LDAP is accessible; if it  is not, then the utility will return a warning of the general form: &#x5b;date-and-time&#x5d; hostname &#x5b;pid&#x5d;: General Warning: could not get server configurat ion in ldap, using cached configuration information and then proceed to attempt to process the address using cached LDAP configuration information. Note that one of the more common cases where the above warning can be issued is where the LDAP server is in fact not  responding, in which case the    utility may further not be able to successfully lookup  "local" domains and users. Then temporary errors of the form 4.0.0 Temporary lookup failure: address (or whatever is configured via the   MTA option)  when attempting to  rewrite addresses suggest that the LDAP user/group directory is  unavailable/unresponsive; further details on the underlying LDAP error  may be obtained using the utility&#x27;s   switch.

,  (default)
(New in MS 8.0)  The   switch may be used to specify an alternate address deliver by value. is the default.

,  (default)
(New in MS 8.0) Specifying  causes any added  prefix or suffix text to be displayed. (That is,  causes display of text added via alias options   or , or via mailing list named parameters   or  , or via LDAP attributes such as    or  .)   is the  default.

If a compiled configuration is not being used, then  normally consults the default alias file during the  rewriting process. Prior to MS 7.0, that alias file was located via the    option of the MTA Tailor file, so usually   ; as of MS 7.0, the alias  file is located as CONFIGROOT. The  switch specifies an alternate file for    to use. This switch has no effect unless   is specified or no compiled  configuration exists; use of a compiled configuration precludes direct  reading of the alias file from any location; this switch also has no effect when an XML configuration is in use.

(New in MS 8.0) Specify an alternate recipient address.

This switch is used to specify the application-info string to use  during, for instance, ,   , and    mapping table probes. For instance, for an incoming SMTP message where the sending client claimed (on its HELO/EHLO line) a hostname of  domain.com, and where TLS was not used, the application-info string  would be " ".

,  (default)
(New in MS 8.0)  The   switch may be used to specify a deliver by (SMTP DELIVERBY extension BY parameter) value. is the default.

(default),
This switch controls whether the utility outputs detailed information, e.g., channel flags, regarding the channel an  address matches.

As of MS 8.0.2.1, this switch accepts an optional channel type, which controls which of the various channels selected by the rewriting process is displayed. Possible values are forward, backward, source, and destionation. The default is forward, which displays the channel selected by rewriting the input address in the "forward" direction. Note that source and destination display channel information for the selected source and destination channels, which are not address-dependent.

,  (default)
This switch controls checking of alias address expansion. Normally the MTA considers the expansion of an alias to have been  "successful" if any of the addresses to which the  alias expands are legal. The  switch  causes a much stricter policy to be applied:   checks each expanded address in  detail and reports a list of any addresses, expanded or otherwise, that  fail to rewrite properly. For addresses that match the L channel, the  MTA also performs validity checks.

If no compiled configuration is being used, then  normally consults the default MTA configuration file  during the rewriting process. Prior to MS 7.0, the MTA configuration file was located via the    option of the MTA Tailor  file, usually pointing to  ;  as of MS 7.0, the MTA configuration file is located at  CONFIGROOT. The   switch specifies an alternate file  to use in place of the regular configuration file. This switch has no effect unless  is specified or no  compiled configuration exists; use of a compiled configuration will  preclude direct reading of the MTA configuration file from any location; this switch also has no effect when an XML configuration is in use.

,
If no compiled configuration is being used, then  normally accesses the default conversion file as part of  its initialization during the rewriting process; while the conversion  file has no particular effect on address rewriting, it is considered  part of the core configuration (and hence   will warn of problems accessing the conversion file, or  of out-of-date versions of the conversion file). Prior to MS 7.0, that default conversion file was located via the    option  of the Tailor file, so usually   ; as of MS 7.0, in legacy configuration the  conversion file is located as  CONFIGROOT ; in Unified Configuration, a separate file is not used and instead  the   MTA option stores the conversions. The   switch specifies an alternate file to  use in place of the regular converison file. These switches have no effect unless   is  specified or no compiled configuration exists; use of a compiled  configuration will preclude direct reading of the conversion file from  any location. Use of the  switch will  prevent the conversion file from being read in when there is  no compiled configuration. These switches also have no effect when an XML configuration is in use.

by default during its operation consults any of the usual MTA databases that it has been configured to  use. (For MTA configuration controlling whether databases are normally used, see the Database MTA options, and in particular the ,   ,   ,   ,  and    MTA  options.) The    switch is used to either disable references to various databases or  to redirect the database paths to nonstandard locations. The allowed list items are ,  ,   ,  ,   ,  ,  ,   ,  ,  ,   , and. The list items beginning with " " disable use of the  corresponding database. The remaining items require an associated value, which is taken to be the name of that database.

,  (default)
The address rewriting process is capable of producing additional, detailed explanations of what actions are taken and why. The   switch enables this output; it is disabled by  default. In cases of problems with address expansion, , especially  , can also  give more details as to the exact nature of the problem; for instance,  the exact LDAP directory error returned in response to a domain lookup  up, the exact LDAP directory error returned in response to a user  lookup, rejection resulting from an  recipient    mapping table, etc.. As of MS 7.0, note that the basic   output will report if address "duplicate  elimination" occurs, via a debug output line of the form: time-stamp:        - Duplicates previous recipient address, merge This may be of particular interest when multiple, comma-separated addresses were provided initially.

,
The  and    switches, which explicitly set the corresponding receipt request  flags, can be useful when testing the handling of receipt requests when  rewriting forwarded addresses or mailing lists.

The  switch controls for which  destination or target channel    rewrites addresses. Some address rewriting is destination channel  specific; this switch allows control of the assumed destination  channel.

,  (default)
(New in MS 6.3.) The  switch may be used to  set an internal flag indicating that ESMTP is in use. In particular, this may be useful when testing   mapping tables that make use  of that flag (the   flag).

(New in MS 6.3p1.) This switch may be used to initialize the MTA&#x27;s internal  alias expansion limit;  this is intended for testing expansion  limit interactions with mailing lists and other MTA facilities.

(New in MS 7.0u2) The  switch may be used to specify the name of a channel to be treated as if it were the  local channel.

,  (default)
The  switch may be used to have   output any  Sieve filters  (personal mailbox,  so-called  "Head of Household",  channel, or system) applicable  for the address in question. Note that a user&#x27;s   attributes  are converted by the MTA into a  Sieve " "  action which is incorporated at  the beginning of the user&#x27;s personal Sieve filter. As of MS 6.1, the filter output will also be labelled as to which Sieve filter it  came from, taking the form (under the addresses under the  " " portion of the output): Filter: &#x3c;type&#x3e; name location &#x5b;addr response-addr&#x5d; &#x5b;owner owner&#x5d; (h) &#x5b;i&#x5d; {j} or as of MS 6.2: Filter: &#x3c;type&#x3e; name location &#x5b;addr response-addr&#x5d; &#x5b;owner owner&#x5d; (h) &#x5b;i&#x5d; )k( {j} where   is either  or  ,   is a  URL to the  location of the Sieve filter (or in the case of the  system filter, as  of the MS 6.2 patch time frame says merely  ),    is the address  to which a  notification would be sent back (usually only relevant and non-null for  the case of    actions,  in which case it is the  envelope From address), and   is the address  of the "owner" of this Sieve filter:  normally the local postmaster address  for system-level (the system and channel) filters, or the  user himself for a personal Sieve filter, or the  specified owner for a  "Head of Household" Sieve  filter. (The three or four, depending upon MTA version, integers in hexadecimal notation following are  internal debug information, showing the location in memory of internal  parts of the Sieve structure.) So for instance, one might see output  such as the following (where additional line breaks have been inserted  for display purposes): Submitted address list: ims-ms uid%hosteddomain1.com@ims-ms-daemon (orig first.last@hosteddomain1.com,      inter first.last@hosteddomain1.com, host ims-ms-daemon) &#x2a;NOTIFY-FAILURES&#x2a; &#x2a;NOTIFY-DELAYS&#x2a; Filter: &#x3c;user&#x3e; name user:uid%hosteddomain1.com@ims-ms-daemon &#x5b;addr uid%hosteddomain1.com@ims-ms-daemon&#x5d; &#x5b;owner uid%hosteddomain1.com@ims-ms-daemon&#x5d; (0x032107f8) &#x5b;0x0322b718&#x5d; )0x0322ae58( {0x03218e98} ...sample filter lines... Filter: &#x3c;system&#x3e; name file:///IMTA_TABLE%3Aims-ms.filter &#x5b;addr &#x5d; &#x5b;owner postmaster@host.domain.com&#x5d; (0x00073af8) &#x5b;0x0009bb28&#x5d; )0x0009b2c0( {0x0009e670} ....sample filter lines... Filter: &#x3c;system&#x3e; name system: &#x5b;addr &#x5d; &#x5b;owner postmaster@host.domain.com&#x5d; (0x00d37158) &#x5b;0x0320de88&#x5d; )0x0320e788( {0x031ec708} header:2000116;0 3  1  :matches  1  "Subject"  1  "ID &#x2a;... t           hanks"  if  8  ;  refuse:2000127;0  1  1  "I think you&#x27;ve se           nt me a virus.%0AMessage rejected on this basis." ; ""  stop ; Note that the  output shows applicable Sieve  filters, that is, which Sieve filters would get evaluated for  this address. But it does not show the actual evaluation of those Sieve filters (as such evaluation can only be done in the context of actual  message processing), thus it does not show what the effect(s) of those  Sieve filters would be.

Must be superuser or the MTA user in order to display  output.

,
The  switch controls what envelope From address is  used for access control probes and mailing list access probes. If this switch is omitted, then any such probes use the postmaster return  address (as set via the    MTA option). Specifying   tells the MTA to use an empty envelope From  address for access probes.

As of MS 7.0.5, note that    (or   ) or    settings that cause  the MTA to attempt a "verification" of the From address can  affect   output: the output will  include a warning if the From address appeared to be problematic,  though the input address will still be rewritten as usual.

,  (default)
The  switch causes the utility to output any  applicable  header trimming option file  associated with the channel of  the destination address. This information will appear after the destination address itself, before any dumped filter information (from  the   switch), hence before the "Submitted  notifications list:" output. is the default. Note that  merely outputs the header  trimming option file; to investigate the potential effect(s) of a  header trimming option file, see instead.

,  (default)
(New in MS 7.0.5)  The   switch tells the utility  to rewrite the parameter value  as a message identifier, rather than as an address. (For instance, in the default mode of addresses, an a@b@c form will be  turned into a %-route form, whereas in   mode a  value of a@b@c would be quoted.)

(default),
When the  switch is specified (the default),    will load the compiled  configuration. Prior to MS 7.0, this compiled configuration was located via the   option in  the MTA tailor file, usually  pointing to. As of MS 7.0, the compiled configuration is located as  CONFIGROOT. When   is specified,   unconditionally ignores any previously compiled  configuration and instead reads configuration information directly from  the various text files.

By default,  takes input from. The  switch may be used to  specify a different source for input.

,  (default)
Specifying  will result in passing any   flag checks in the   mapping table or recipient address   mapping tables.

,  (default)
(New in MS 6.3.) The  switch may be used to  set an internal flag indicating that LMTP is in use. In particular, this may be useful when testing   mapping tables that make use  of that flag (the   flag).

,  (default)
This switch controls the setting of an alias for the local host. The MTA supports multiple "identities" for the local host; the  local host may have a different identity on each channel. This switch may be used to set the    to the specified  value; appearances of the local host in rewritten addresses will be  replaced by this value.

,
(New in 8.0.1.2) Normally the specified address is presented to the enqueue machinery all at once. Specifying  causes the argument to be treated as a comma-separated list of addresses; each address will be presented for enqueue processing separately, simulating the effect of multiple RCPT TOs.

The MTA&#x27;s enqueue facilities handle the submission of multiple addresses at the same time as an extension. Specifying  disables this capability; multiple addresses will be considered an error.

&#x5b; &#x5d;,
If no compiled configuration is being used, then this switch instructs   to use the specified  mapping file rather than the default mapping file. Prior to MS 7.0, the default mapping file was located via the    option in  the MTA tailor file, so usually   ; as of MS 7.0, in legacy configuration the mappings  file is located as CONFIGROOT ; in  Unified Configuration, a separate file is not used and instead mappings are stored under named   groups. These switches have no effect unless  was  specified or no compiled configuration exists; use of any compiled  configuration will preclude direct reading of the mappings file. Use of the   switch will prevent the  MTA mapping file from being read in when there is no compiled  configuration. These switches also have no effect when an XML configuration is in use.

,  (default)
(New in MS 8.0)    takes a required integer  argument specifying the initial MT-PRIORITY value.

&#x5b; &#x5d;,
If no compiled configuration is being used, then the   switch instructs   to use the specified option file rather than the  default location MTA option file. Prior to MS 7.0, the MTA option file was located via the    option in the  MTA Tailor file, so  usually  ; as of MS 7.0,  in legacy configuration the MTA option file is located at  CONFIGROOT ; in Unified Configuration, a separate file is not used and instead these are  MTA options. These switches have no effect unless   is specified or no  compiled configuration exists; use of any compiled configuration will  preclude direct reading of the MTA option file from any location. Use of the   switch will prevent the MTA option  file from being read in when there is no compiled  configuration. These switches have no effect when an XML configuration is in use.

By default,  writes output to. The  switch may be used to  direct the output of   elsewhere.

Used to specify the password for a password-protected list.

A prompt will appear that allows the password to be entered without echo.

,  (default)
(New in MS 6.3.) The  switch may be used to  set an internal flag indicating that proxy authentication  (POP-before-SMTP) is in use. In particular, this may be useful when testing   mapping tables that make use of that flag (the    flag).

(default),
(New in MS 8.0.1.2.) The  switch controls whether or not the alias expansion process treats an account&#x27;s overquota status as an error. is the default;  may be used to disable the check. This may be useful in simulating the behavior of temporary failure reenqueue operations, which disable this check.

,
The  and    switches, which explicitly set the corresponding receipt request  flags, can be useful when testing the handling of receipt requests when  rewriting forwarded addresses or mailing lists.

(default),
By default, the  utility runs as if the    switch is set, meaning that some operations  that would normally be deferred for "off-line" execution by  the reprocess channel  will instead be performed directly by the test  address processing. may be used to tell the utility to run in a mode more similar to that of a  "normal" channel, where various operations (e.g.,  mailing list password lookups)  will not be performed by the channel,  and where instead the message will be forcibly routed to the reprocess  channel which is expected to perform the necessary tasks later  ("off-line").

This switch controls the setting of the restricted flag. By default, this flag has value 0. When set to 1, i.e.,, the  restricted flag will be set on and addresses will be rewritten using  the restricted mailbox encoding format recommended by RFC 1137. This flag is used to force rewriting of address mailbox names in accordance with the RFC 1137 specifications; see the   channel option for further details.

,
(New in MS 8.0) The  switch is used to specify an RRVS value (Require-Recipient-Valid-Since: value), in  ISO 8601 format. is the default.

,  (default)
(New in MS 6.2p8.) The  switch may be used to  set an internal flag indicating that SASL authentication (SMTP AUTH) is  in use. In particular, this may be useful when testing   mapping  tables that make use of that flag (the    flag).

,  (default)
New in MS 6.2. The  switch may be used to  set the "authenticated sender" field, for use in     mapping table probes.

,  (default)
(New in MS 7.0.5)  The   switch sets an assumed  "message size" (in bytes), as if the SMTP SIZE extension had  been used. It requires an integer argument, which the MTA interprets as being in units of bytes. This can be useful for checking message size-based restrictions. is the default.

,  (default)
(New in MS 7.0 update 2.) Control whether or not to show per-recipient spamfilter "opt-in".

Must be superuser or the MTA user in order to display  output.

The  switch controls which source  channel to assume when rewriting addresses. Some address rewriting is source channel specific;    by default assumes that the channel  source for  which it is rewriting is the local channel,    on UNIX.

,  (default)
(New in MS 7.0 update 2.) Control whether or not to show per-recipient "spare" LDAP attributes.

Must be superuser or the MTA user in order to display  output.

,  (default)
The  switch can be used to tell the MTA to  output the  direct LDAP lookup cache  statistics for the rewriting performed; statistics for the domain cache, reverse cache, and alias  cache will be displayed. is the default.

The -srs switch provides a way to override certain SRS-related MTA configuration options: The  value overrides the   MTA option, the   value overrides the   MTA option, and the   value overrides the   value.

Additionally, specification of -nosrs causes test -rewrite to act as it none of the  options are set.

,
If no compiled configuration is being used, then  normally consults the default system Sieve filter during  the rewriting process: this is the    MTA option in Unified Configuration, or the system filter file in legacy configuration. Prior to MS 7.0, the MTA system filter file was located via the     option of the MTA Tailor file, so  usually  ; as of MS 7.0,  the MTA system filter file is located as  CONFIGROOT. The   switch specifies an alternate file to  use in place of the default system Sieve filter file. These switches have no effect unless  is   specified or no compiled configuration exists; use of a compiled  configuration will preclude direct reading of the system filter file  from any location. Use of the  switch  will prevent the MTA system filter file (legacy configuration) from being read in when  there is no compiled configuration. These switches have no effect when an XML configuration is in use.

,  (default)
(New in MS 7.0.5)  The   switch can be used to set the  conversion tag  (or comma-separated list of tags) that will be available  at the time of    mapping table probes. This can be useful when bit 8 (value 256) of the     MTA option is set, so  that   mapping table probes include conversion tags.

,  (default)
(New in MS 6.2p8.) The  switch may be used to  set an internal flag indicating that TLS is in use. In particular, this may be useful when testing   mapping tables that make use of  that flag (the   flag).

This switch is used to specify the transport-info string to use  during, for instance,  ,   , and    mapping table probes. (Note that the  mapping table is  not checked by the , as the    mapping table is consulted for decisions regarding TCP/IP  connections, rather than for address handling; in particular the    mapping table is used by the  Dispatcher, and then again by  SMTP server processes, at a much earlier stage of processing than the  address rewriting process.) Note that a typical transport-info string,  of the form TCP&#x7c;server-address&#x7c;server-port&#x7c;client-address&#x7c;client-port contains vertical bar characters,, which will require  some quoting to pass through the shell; e.g., -transportinfo=TCP\&#x7c;123.45.67.8\&#x7c;12435\&#x7c;10.0.0.1\&#x7c;25

&#x5b; &#x5d;
(New in MS 7.0.)  normally reads its  configuration from , if such a file  exists. The  switch specifies use of a Unified Configuration (which is the MTA&#x27;s default behavior if   exists), and  optionally specifies an alternate, XML  format, configuration file to use in place of.

Examples
This UNIX example shows typical output generated by  in MS 6.3. Perhaps the single most important piece of information generated by   is  displayed on the last few lines of the output,  (6), showing the channel to which   would  submit a message with the specified test address and the form in which  the test address would be rewritten for that channel. This output is invaluable when debugging configuration problems. % imsimta test -rewrite dan@innosoft.com channel               = tcp_local        (1) channel description   = channel caption       = channel user filter   = dest channel filter   = source channel filter = channel flags #0      = BIDIRECTIONAL SINGLE_SYSTEM IMMNORMAL NOSERVICEALL (2) channel flags #1      = SMTP_CRLF MX IDENTNONENUMERIC DEFAULT channel flags #2      = COPYSENDPOST COPYWARNPOST POSTHEADBODY HEADERINC NOEXPROUTE channel flags #3      = LOGGING NORESTRICTED RETAINSECURITYMULTIPARTS channel flags #4      = EIGHTNEGOTIATE HEADERKEEPORDER NOHEADERREAD RULES channel flags #5      = TRUNCATESMTPLONGLINES channel flags #6      = LOCALUSER REPORTNOTARY channel flags #7      = SWITCHCHANNEL REMOTEHOST DATEFOUR DAYOFWEEK channel flags #8      = NODEFRAGMENT EXQUOTA REVERSE NOCONVERT_OCTET_STREAM channel flags #9      = NOTHURMAN INTERPRETENCODING USEINTERMEDIATE RECEIVEDFROM VALIDATELOCALNONE NOTURN defaulthost           = domain.com domain.com linelength            = 998 addrsperfile          = 99 channel env addr type = SOURCEROUTE channel hdr addr type = SOURCEROUTE channel official host = tcp-daemon       (3) channel queue 0 name  = SMTP_POOL channel queue 1 name  = SMTP_POOL channel queue 2 name  = SMTP_POOL channel queue 3 name  = SMTP_POOL channel after params  = channel user name     = urgentnotices         = 1 2 4 7 normalnotices         = 1 2 4 7 nonurgentnotices      = 1 2 4 7 channel rightslist ids =                      (4) local behavior flags  = %x0 expandchannel         = notificationchannel   = dispositionchannel    = tlsswitchchannel      = backward channel      = tcp_local        (5) unique identifier     = dan@innosoft.com header forward address = dan@innosoft.com (route (TCP-DAEMON,TCP-DAEMON)) (host innosoft.com) header reverse address = dan@innosoft.com envelope forw address = dan@innosoft.com  (route (TCP-DAEMON,TCP-DAEMON)) (host innosoft.com) envelope rev address  = dan@innosoft.com  (route (TCP-DAEMON,TCP-DAEMON)) (host innosoft.com) name                  = mbox                  = dan Extracted address action list: dan@innosoft.com Extracted 733 address action list: dan@innosoft.com Address list expansion: -13 expansion total. Expanded address: dan@innosoft.com Submitted address list:                    <span id='call_063'> (6) tcp_local dan@innosoft.com (orig dan@innosoft.com, host innosoft.com) &#x2a;NOTIFY-FAILURES&#x2a; &#x2a;NOTIFY-DELAYS&#x2a; Submitted notifications list:              (7) <ol>

 <span id='call_064'> The channel to which, after rewriting as an   envelope To address, the address is mapped. </li>

 <span id='call_065'> The flags set for the channel indicated in   (1). These flags are controlled by the   channel options set on the channel (in legacy    configuration, those channel    options set on the first line of the channel control block for the    specified channel). Any unknown options---options which may have been   mistyped---will be interpreted as group ids and will appear on the line    (4). </li>

 <span id='call_066'> The channel&#x27;s official host name as   specified on the second line of the channel control block for the    channel indicated in (1). </li>

 <span id='call_067'> Any items appearing on the first line of the   channel block which were not channel options are interpreted as group    ids. Any group ids so specified for the channel are listed on this line. </li>

 <span id='call_068'> The channel which the address would match if   rewritten as an envelope From address. </li>

 <span id='call_069'> The channel to which a message with the   address dan@innosoft.com would be queued and the envelope To address    which would be used. Here, the message would be submitted to the TCP/IP   channel, , using the address dan@innosoft.com. Other information appearing here might include an explicit Errors-to:   address, which, if present, appears enclosed in square brackets; or    notations such as   or , indicating    whether or not the message is flagged for read receipts, or notations    such as  ,  ,     , etc., indicating the    message&#x27;s delivery receipt mechanism and flagging. </li>

 <span id='call_070'> Notification addresses. If notifications   need to be generated regarding this address, as for instance in the    case of a group or list whose definition includes some (immediately    obvious as such) bad addresses, then the addresses about which a    notification needs to be generated will be listed here, along with the    error corresponding to each such address. If an override envelope From   is in effect for the original message, hence if the notification will    go back to some address other than the original message&#x27;s sender, then    that address (the address to which the notification will be sent) will    be shown enclosed in square brackets. Note that the recipient address   for the notification will only be shown if it is something different    than the original sender address (as specified via the      switch, or defaulting to the    postmaster address). New in MS 7.0u2,    the word " " will appear within    such square brackets, to emphasize that the address shown is the    address to which the notification will be sent. </li>

</ol>

The example below shows typical output generated by  in MS 8.0. % imsimta test -rewrite dan@innosoft.com address channel       = tcp_local                       (1) forward channel       = tcp_local                       <span id='ref_072'> (2) channel description   = channel caption       = channel user filter   = dest channel filter   = source channel filter = phase filter = channel flags #0      = BIDIRECTIONAL MULTIPLE IMMNONURGENT NOSERVICEALL  (3) channel flags #1      = SMTP_CRLF AFFINITYLIST IDENTNONENUMERIC DEFAULTDKIMIGNORE channel flags #2      = NOSENDPOST NOWARNPOST POSTHEADBODY HEADERINC NOEXPROUTE channel flags #3      = LOGGING NORESTRICTED RETAINSECURITYMULTIPARTS channel flags #4      = UTF8NEGOTIATE HEADERKEEPORDER NOHEADERREAD RULES channel flags #5      = TRUNCATESMTPLONGLINES defaulthost           = domain.com domain.com linelength            = 998 addrsperfile          = 99 channel env addr type = SOURCEROUTE channel hdr addr type = SOURCEROUTE channel official host = tcp-daemon                      (4) channel queue 0 name  = SMTP_POOL channel queue 1 name  = SMTP_POOL channel queue 2 name  = SMTP_POOL channel queue 3 name  = SMTP_POOL channel after params   = channel daemon name   = outgate.domain.com channel user name     = urgentnotices         = 1 2 4 7 normalnotices         = 1 2 4 7 nonurgentnotices      = 1 2 4 7 local behavior flags  = %x0 expandchannel         = notificationchannel   = dispositionchannel    = backward channel      = tcp_local                       (5) unique identifier     = dan@innosoft.com header forward address = dan@innosoft.com (route (TCP-DAEMON,TCP-DAEMON)) (host innosoft.com) header reverse address = dan@innosoft.com envelope forw address = dan@innosoft.com  (route (TCP-DAEMON,TCP-DAEMON)) (host innosoft.com) envelope rev address  = dan@innosoft.com  (route (TCP-DAEMON,TCP-DAEMON)) (host innosoft.com) name                  = mbox                  = dan Extracted address action list: dan@innosoft.com Extracted 733 address action list: dan@innosoft.com Address list expansion: -13 expansion total. Expanded address: dan@innosoft.com Submitted address list:                                   (6) tcp_local dan@innosoft.com (orig dan@innosoft.com, host innosoft.com) &#x2a;NOTIFY-FAILURES&#x2a; &#x2a;NOTIFY-DELAYS&#x2a; 4 Submitted notifications list:                             (7) # <ol>

 <span id='call_071'> The channel to which, after performing any   address reversal,     the address matches an an envelope From address. </li>

 <span id='call_072'> The channel which, rewriting as an envelope   To address, the address matches. </li>

 <span id='call_073'> The   channel options set for the channel    indicated in (2). </li>

 <span id='call_074'> The channel&#x27;s official host name as   specified by the      option    (Unified Configuration)    or the second line of the channel block (legacy configuration) for the    channel indicated in (2). </li>

 <span id='call_075'> The channel which the address would match if   rewritten as an envelope From address. </li>

 <span id='call_076'> The channel to which a message with the   address   would be queued and the envelope To address    which would be used. Here, the message would be submitted to the   TCP/IP    channel   using the address. Other information appearing here might   include an explicit Errors-to: address, which, if present, appears    enclosed in square brackets; or notations such as   or    , indicating whether or not the message is flagged    for read receipts, or notations such as  ,     ,  ,    etc., indicating the message&#x27;s delivery receipt mechanism and    flagging. </li>

<li> <span id='call_077'> Notification addresses. If   notifications    need to be generated regarding this address, as for instance in the    case of a group or list whose definition includes some (immediately    obvious as such) bad addresses, then the addresses about which a    notification needs to be generated will be listed here, along with the    error corresponding to each such address. If an override envelope From   is in effect for the original message, hence if the notification will    go back to some address other than the original message&#x27;s sender, then    that address (the address to which the notification will be sent) will    be shown enclosed in square brackets. Note that the recipient address   for the notification will only be shown if it is something different    than the original sender address (as specified via the      switch, or defaulting to the    postmaster address). </li>

</ol>

Error messages
Usually errors reported by  are not  actually errors regarding   in  particular, but rather are the utility warning of an underlying  configuration problem. For instance, " ..." sorts of errors are typically configuration errors (whether errors of syntax, of access, of inconsistent/incompatible settings, etc.). Address list error -- unknown host or domain: The above error indicates that the domain name in the specified address did not rewrite to any MTA channel. Check that the domain name was correctly spelled. If the domain name was correct and was a locally hosted domain, then most likely it is not correctly provisioned as a  domain in LDAP; see the Schema Reference. If the domain name was a correctly spelled external domain name, then most likely you need a new  (or changed)  rewrite rule in the MTA configuration to handle that  domain name, or an updated   file; see  TLD comparison rewrites. Unknown group identifier ... found on channel ... Prior to MS 7.0, any word on a channel not recognized as a channel option was  interpreted as a group identifier. So prior to MS 7.0, the above error was possible, meaning that you (the executor of the   command) do not have the specified group identifier. Check that the word shown is truly intended to be present as a group identifier, rather than simply being a misspelled channel option.

See also:
 * cnbuild utility
 * Aliases
 * Mailing lists
 * Address reversal
 * Recipient access mapping tables
 * FROM_ACCESS mapping table
 * Sieve filters
 * SRS MTA options
 * Alias file named parameters
 * Alias options
 * Direct LDAP attribute name MTA options
 * Postmaster addresses
 * return_address MTA Option
 * domain_failure MTA Option
 * MTA Tailor options
 * conversions MTA Option
 * Database MTA options
 * Head of household Sieve filters
 * systemfilter MTA Option
 * Sieve vacation extension
 * Sieve language
 * returnenvelope Option
 * mailfromdnsverify Option
 * return_envelope MTA Option
 * test -header utility
 * The mapping group
 * Password-protected mailing lists
 * Process and reprocess channels
 * restricted Option
 * Spam and virus filtering
 * LDAP lookup cache MTA options
 * Conversion tags
 * REVERSE mapping table
 * include_conversiontag MTA Option
 * Channel options
 * official_host_name Option
 * Typical TCPIP channels and servers
 * Notification message generation timing
 * MTA command line utilities