Test -domain map utility

Test a domain (domain map) lookup.

Syntax
imsimta test -domain_map &#x5b;expression&#x5d;

Description
is an interactive utility for testing how domains are provisioned in LDAP.

Especially common uses/commands to use are to list (properly) provisioned domains in LDAP using the  command, or verify proper (as regards MTA requirements) provisioning of domains in LDAP using the   command.

Targetted probing of specific domain definitions can also be performed. A base command sequence is to  and then   a domain: DOMAIN_MAP&#x3e; LOCATE DOMAIN mrochek.com Entry located DOMAIN_MAP&#x3e; SHOW Domain name: mrochek.com Canonical name: mrochek.com Lower case canonical name: mrochek.com Base DN: o=mrochek.com,o=usergroup Domain DN: dc=mrochek,dc=com,o=internet After locating a domain, you can probe the value of a specific basic attributes: DOMAIN_MAP&#x3e; LOCATE DOMAIN mrochek.com Entry located DOMAIN_MAP&#x3e; QUERY inetDomainBaseDN Attribute value(s): &#x5b;0&#x5d; "o=doof,o-mrochek.org,o=usergroup" DOMAIN_MAP&#x3e; QUERY inetCanonicalDomainName Attribute value(s): &#x5b;0&#x5d; "mrochek.org" If you wish to know about other than the couple of basic attributes, then you have to let the utility know about such attributes via the  command before doing the. E.g., DOMAIN_MAP&#x3e; LOCATE DOMAIN mrochek.com Entry located DOMAIN_MAP&#x3e; QUERY creatorsname Not on known attribute list DOMAIN_MAP&#x3e; ATTRIBUTE creatorsname Attribute now known to map DOMAIN_MAP&#x3e; LOCATE DOMAIN mrochek.com Entry located DOMAIN_MAP&#x3e; QUERY creatorsname Attribute value(s): &#x5b;0&#x5d; "cn=directory manager"

Commands
commandsshows the interactive commands available.

Error messages
Below are listed possible warnings and errors that may be reported. Note that "errors" are reported when a domain is defined in a way not  suitable for MTA use as an  addressing or routing domain;  however, if a  domain is defined in LDAP for use by some component(s) other than (not  including) Messaging Server, then it is not necessarily an  error to have a domain defined in a fashion inappropriate for MTA  domain usage. That is, reports of "errors" regarding domain definitions must be interpreted in light of a site&#x27;s intended usage of  domains: errors reported regarding domains used by the MTA are  definitely problems, but "errors" reported regarding other  domains must be interpreted in light of such a domain&#x27;s intended usage. Missing, empty, invalid or duplicate entry 

 Facility: General 

 Severity: Error 

 Explanation: Problem with a domain entry 

 Identifier too long 

 Facility: General (e.g.,   ) 

 Severity: Error 

 Explanation: Specified domain name was too long. 

 Attribute not listed 

 Facility: General (e.g.,   ) </li>

 Severity: Error </li>

 Explanation: Specified attribute not found in domain entry. </li>

</ul> LDAP error 

 Facility: General </li>

 Severity: Error </li>

 Explanation: Trouble communicating with LDAP. </li>

</ul> Bad schema level 

 Facility: General </li>

 Severity: Error </li>

 Explanation: Schema mode other than 1 or 2 specified. </li>

</ul> %DMAP-E-ALIASANDBASEDN, Domain alias entry &#x27;domain-name&#x27; also contains a base DN 

 Facility: </li>

 Severity: Error </li>

 Explanation: The supposed domain alias entry has an   LDAP attribute (in the case of the MTA,  more precisely, whatever LDAP attribute is named by the     MTA option), which is an attribute that ought  only to be present on an actual domain entry, not on a domain alias  entry. </li>

<li> User Action: If this domain entry is truly intended as a domain alias entry, then remove the    LDAP attribute from it (while also making sure that the real domain  entry does have an   attribute present). If, however, this domain entry ought instead to be its own, real domain entry, then remove the LDAP attributes (such as   )  that are setting it up as a domain alias entry. </li>

</ul> %DMAP-E-ALIASTOOLONG, Domain alias &#x27;domain-name&#x27; in entry with DN &#x27;DN-string&#x27; is too long <ul>

<li> Facility: </li>

<li> Severity: Error </li>

<li> Explanation: The domain entry has a   LDAP attribute (or for the MTA, more  precisely whatever LDAP attribute is named by the     MTA option) with a value longer than 1024 characters. </li>

<li> User Action: Shorten the   value. </li>

</ul> %DMAP-E-BASEDNTOOLONG, Base DN &#x27;DN-string&#x27; in base entry for domain &#x27;domain-name&#x27; is too long <ul>

<li> Facility: </li>

<li> Severity: Error </li>

<li> Explanation: Schema 2. This domain entry has no explicit   (optional in Schema 2) and the  DN of this domain entry, when converted to a string, is longer than  1024 characters. </li>

<li> User Action: One possibility is to add an explicit   attribute  (or more precisely, for the MTA add whatever attribute is named by the    MTA option) specifying where users/groups  in this domain are stored in the DIT; while this may work around this  immediate issue, note that if the DNs in your DIT are long enough to  trigger this error, then you may encounter other processing  difficulties due to the "long" DNs. Alternatively, shorten the DNs for your domains; this may require some restructuring of your  domain names or DIT, but lead to more satisfactory processing in  general. </li>

</ul> %DMAP-E-BASEDNTOOLONG, Base DN pointer &#x27;DN-string&#x27; in entry for domain &#x27;domain-name&#x27; is too long <ul>

<li> Facility: </li>

<li> Severity: Error </li>

<li> Explanation: The  value  (for the MTA, more precisely the value of whatever attribute is named  by the     MTA option) is longer than 1024  characters. </li>

<li> User Action: Shorten the , restructuring the data in the directory,  if necessary. </li>

</ul> %DMAP-E-CANONICAL, Overlapping domains &#x27;domain-name-1&#x27; and &#x27;domain-name-2&#x27; defined by entries &#x27;DN-1&#x27; and &#x27;DN-2&#x27; have different canonical domains &#x27;canon-name-1&#x27; and &#x27;canon-name-2&#x27; <ul>

<li> Facility: </li>

<li> Severity: Error </li>

<li> Explanation: The domain name usage is not consistent: domains with overlapping sets of users have conflicting "canonical" domain names. </li>

<li> User Action: Check the structuring of the domains, especially the use of the  and   LDAP domain attributes (or more precisely, the attributes named by the   and   MTA options). </li>

</ul> %DMAP-E-CANONICALINVALID, Canonical domain &#x27;canon-name&#x27; defined/referenced by domain entry with DN &#x27;dn-string&#x27; is syntactically invalid <ul>

<li> Facility: </li>

<li> Severity: Error </li>

<li> Explanation: The   domain attribute (or more precisely, the LDAP domain attribute named by the   MTA option) has a value which is not syntactically valid as a domain name. </li>

<li> User Action: Ensure that the canonical domain name is a syntactically valid, fully-qualified, Internet domain name. (Note that a not-fully-qualified domain name, a "short form" host name, will instead result in the error below: .) </li>

</ul> %DMAP-E-CANONICALSHORTFORM, Short form canonical domain &#x27;domain-name&#x27; defined/reference by domain entry with DN &#x27;dn-string&#x27; <ul>

<li> Facility: </li>

<li> Severity: Error </li>

<li> Explanation: The   (or more precisely, the LDAP domain attribute named by the   MTA option) has its value set to a "short form" host name value rather than a fully qualified domain name. </li>

<li> User Action: Change the value to be a fully qualified domain name. There are some places where it is acceptable to use a "short form" host name, but the canonical domain name should be a fully qualified domain name. </li>

</ul> %DMAP-E-CANONICALTOOLONG, Canonical name &#x27;canon-name&#x27; in entry for domain &#x27;domain-name&#x27; is too long <ul>

<li> Facility: </li>

<li> Severity: Error </li>

<li> Explanation: The   domain attribute (or more precisely, the LDAP domain attribute named by the   MTA option) has a value longer than 1024 characters. </li>

<li> User Action: Shorten the canonical domain name. </li>

</ul> %DMAP-E-CANTCONVDCDN, Cannot convert alias pointer DN &#x27;aliasedObjectName-value&#x27; for domain alias domain-name to  domain name <ul>

<li> Facility: </li>

<li> Severity: Error </li>

<li> Explanation: The DN specified by the   LDAP attribute (in the case of the MTA,  more precisely, whatever LDAP attribute is named by the     MTA option), could not be processed to produce a  domain name; presumably it was not of a organization sort of  form. </li>

<li> User Action: Check that the   value is correctly specified. </li>

</ul> %DMAP-E-CANTCONVDCDN, Cannot convert DN &#x27;dn-string&#x27; in DC tree to domain name <ul>

<li> Facility: </li>

<li> Severity: Error </li>

<li> Explanation: A failure occurred attempting to convert the domain&#x27;s DN into a domain name. </li>

<li> User Action: Check the LDAP domain structure. </li>

</ul> %DMAP-E-CANTEXTALIAS, Empty alias pointer attribute in &#x27;domain-name&#x27; domain alias entry <ul>

<li> Facility: </li>

<li> Severity: Error </li>

<li> Explanation: The supposed domain alias entry has no   LDAP attribute (in the case of the MTA,  more precisely, none of whatever LDAP attribute is named by the     MTA option). </li>

<li> User Action: Add an   attribute pointing to a "real" domain entry. </li>

</ul> %DMAP-F-CANTGETDN, Cannot obtain DN of domain entry, directory error <ul>

<li> Facility: routine (called by,  e.g.,  ) </li>

<li> Severity: Fatal </li>

<li> Explanation: An unexpected error: something "wrong" has happened with the data in the LDAP directory, or  with retrieval and basic handling of that data. </li>

<li> User action: There may be something seriously wrong with the LDAP directory. Verify that the LDAP directory is operating and its data is uncorrupted. </li>

</ul> %DMAP-W-DISALLOWEDATTR, Domain &#x27;domain-name&#x27; has a disallowed attribute &#x27;attr-name&#x27; with value &#x27;string&#x27; <ul>

<li> Facility: </li>

<li> Severity: Warning </li>

<li> Explanation: The   domain attribute is present (and has a value set). </li>

<li> User Action: Remove the attribute. </li>

</ul> %DMAP-E-DNTOOLONG, Domain entry DN beginning with &#x27;dn-string&#x27; is too long <ul>

<li> Facility: routine (called by,  e.g.,  ) </li>

<li> Severity: Error </li>

<li> Explanation: The DN for this domain is longer than the maximum permitted DN length (1024 characters). </li>

<li> User action: If this domain is one that it is desired that the MTA make use of (say in addressing or routing), then change  its DN to something shorter; this may require some restructuring of  data and entries in LDAP. </li>

</ul> %DMAP-E-DOMAINALIASINVALID, Domain alias &#x27;string&#x27; defined/referenced by domain entry with DN &#x27;DN-string&#x27; is syntactically invalid <ul>

<li> Facility: </li>

<li> Severity: Error </li>

<li> Explanation: A domain alias, whether found via  pointer in Schema 1 mode, or set as a   in Schema 2 mode, (see the    or   MTA options) is not a syntactically valid domain name. </li>

<li> User Action: Correct the domain alias. </li>

</ul> %DMAP-E-DOMAININVALID, Domain name &#x27;domain-name&#x27; defined/referenced by domain entry with DN &#x27;DN-string&#x27; is syntactically invalid <ul>

<li> Facility: </li>

<li> Severity: Error </li>

<li> Explanation: The domain name (whether constructed from the " " chunks in the   in Schema 1 mode, or found in the     attribute in Schema 2 mode) is not syntactically valid. </li>

<li> User Action: Correct the domain entry. </li>

</ul> %DMAP-E-DOMAINMULTDEF, Domain &#x27;domain-name&#x27; multiply defined by entries with DNs &#x27;DN-string-1&#x27; and &#x27;DN-string-2&#x27; <ul>

<li> Facility: </li>

<li> Severity: Error </li>

<li> Explanation: Two different domain entries in Schema 2 mode both claim the same domain name, that is, have the same value in either of their  respective   or    LDAP attributes (or for the MTA, more  precisely whatever LDAP attributes are named by the     and     MTA options). </li>

<li> User Action: Correct the domain entries so that each domain entry has its own, unique, domain name (its own, unique,    value) and so that different domain  entries do not claim the same domain alias (same    value). Note that it is perfectly normal and legitimate to have domain aliases, and overlapping domain name  usage is also legitimate and supported -- but there are correct ways to  provision such usage. A domain alias is configured in Schema 2 via use of the   LDAP attribute on the real domain  entry. Overlapping domain name usage is configured by use of distinct domain entries that specify and control overlap via    and    LDAP  attributes. </li>

</ul> %DMAP-E-DOMAINTOOLONG, Domain &#x27;domain-name&#x27; in entry with DN &#x27;DN-string&#x27; is too long <ul>

<li> Facility: </li>

<li> Severity: Error </li>

<li> Explanation: The domain entry&#x27;s (Schema 2 mode) domain name, that is, the value in its   LDAP attribute (or for  the MTA, more precisely whatever LDAP attribute is named by the     MTA option), is longer than 1024 characters. </li>

<li> User Action: Shorten the   value so that it is at most 1024  characters long. </li>

</ul> %DMAP-E-DOMAINUNDEF, Domain name &#x27;domain-name&#x27; referenced by domain entry with DN &#x27;DN-string&#x27; never defined <ul>

<li> Facility: </li>

<li> Severity: Error </li>

<li> Explanation: The domain name usage is not consistent; an undefined domain name has been found. </li>

<li> User Action: Check the list of domains that can be properly located in the directory (see for instance the   command of  ),  and compare with the list of domains you desire to have defined: look for any "orphan" (undefined/not located) domain name. </li>

</ul> %DMAP-W-EMPAPPSTAT, Domain &#x27;domain-name&#x27; has an empty application status <ul>

<li> Facility: </li>

<li> Severity: Warning </li>

<li> Explanation: The   domain attribute (or more precisely, the LDAP domain attribute named by the   MTA option) is present but with no value set. </li>

<li> User Action: The MTA interprets a missing value as meaning " ", but a valid value should be set (especially as non-MTA components may have other behaviors upon failing to find a valid value). </li>

</ul> %DMAP-W-EMPDEFMAILHOST, Domain &#x27;domain-name&#x27; has an empty mailHost default <ul>

<li> Facility: </li>

<li> Severity: Warning </li>

<li> Explanation: The domain LDAP attribute named by the    MTA option (not set by default) is present, but has no value set. </li>

<li> User Action: Set a valid value, or remove the attribute. </li>

</ul> %DMAP-W-EMPDISALLOWED, Domain &#x27;domain-name&#x27; has an empty disallowed attribute <ul>

<li> Facility: </li>

<li> Severity: Warning </li>

<li> Explanation: The   domain attribute is present, but with no value set. </li>

<li> User Action: Remove the attribute. </li>

</ul> %DMAP-W-EMPDOMSTAT, Domain &#x27;domain-name&#x27; base node at DN-string has an empty domain status <ul>

<li> Facility: </li>

<li> Severity: Warning </li>

<li> Explanation: Schema 2. The domain entry has no   attribute, or such an attribute has no  value set. (For MTA purposes, more precisely the attribute named by the    MTA option is not present or is present but  with no value set.) Processing will continue after this warning; indeed  the MTA treats such a missing attribute or empty value as equivalent to  a setting of. </li>

<li> User Action: Consider setting   to a value of   for  clarity (and to avoid this warning). </li>

</ul> %DMAP-E-EMPTYBASEDN, Domain &#x27;domain-name&#x27; has an empty base DN <ul>

<li> Facility: </li>

<li> Severity: Error </li>

<li> Explanation: The domain entry has an  attribute (or for the MTA, more precisely whatever attribute is named by the    MTA option), but with no value set for that attribute. </li>

<li> User Action: In Schema 1 mode, this attribute must be present and must have a value: set a value for the attribute. In Schema 2 mode, this presence of this attribute is optional, but if present it must have a value: either remove the attribute entirely (if the user entries are all located directly under the domain entry), or set a correct value for the attribute. </li>

</ul> %DMAP-E-EMPTYCANONICAL, Domain &#x27;domain-name&#x27; has an empty canonical name <ul>

<li> Facility: </li>

<li> Severity: Error </li>

<li> Explanation: The   domain attribute (or more precisely, the LDAP domain attribute named by the   MTA option) is present but does not have a value. </li>

<li> User Action: Either remove the attribute, or set a valid value for it. </li>

</ul> %DMAP-W-EMPUIDSEP, Domain &#x27;domain-name&#x27; has an empty UID separator attribute <ul>

<li> Facility: </li>

<li> Severity: Warning </li>

<li> Explanation: The   domain attribute  (or more precisely, the LDAP attribute named by the   MTA option) is present, but with no value set. </li>

<li> User Action: Set a valid value, or remove the attribute. Note that while the MTA doesn&#x27;t directly use the value, the authentication library code  does make use of the attribute&#x27;s value. </li>

</ul> %DMAP-F-INTDEFERROR, Internal defined flag error on domain &#x27;domain-name&#x27;, aborting <ul>

<li> Facility: </li>

<li> Severity: Fatal </li>

<li> Explanation: The code encountered a problem with its internal hashed storage of domain names, possibly a coding error. </li>

<li> User Action: Report this error to Oracle. </li>

</ul> %DMAP-F-INTHASHERROR, Internal hash error, aborting <ul>

<li> Facility: </li>

<li> Severity: Fatal </li>

<li> Explanation: The code encountered a problem with its internal hashed storage of domain names or domain base DNs, possibly a  coding error. </li>

<li> User Action: Report this error to Oracle. </li>

</ul> %DMAP-F-INTHASHERROR, Internal tree structure error, aborting <ul>

<li> Facility: </li>

<li> Severity: Fatal </li>

<li> Explanation: The code encountered a problem with its domain tree structure, possibly a coding error. </li>

<li> User Action: Report this error to Oracle. </li>

</ul> %DMAP-F-INTTREESTRUCTERROR, Internal tree structure error, aborting <ul>

<li> Facility: </li>

<li> Severity: Fatal </li>

<li> Explanation: The code encountered a problem with its domain tree structure, possibly a coding error. </li>

<li> User Action: Report this error to Oracle. </li>

</ul> %DMAP-W-INVALIDAPPSTAT, Application status &#x27;string&#x27; for domain &#x27;domain-name&#x27; is invalid <ul>

<li> Facility: </li>

<li> Severity: Warning </li>

<li> Explanation: The   domain attribute (or more precisely, the LDAP domain attribute named by the   MTA option) has an invalid value set: a value which is none of ,  ,  ,  ,  ,  ,  ,  , or. </li>

<li> User Action: Set a valid value. Although the MTA will interpret invalid values as meaning " ", it is unwise to rely on that effect when other components with other behavior may also interpret (and interpret differently) the attribute&#x27;s value. </li>

</ul> %DMAP-E-INVALIDBASEDN, Base DN pointer &#x27;DN-string&#x27; in entry for domain &#x27;domain-name&#x27; is not a valid DN <ul>

<li> Facility: </li>

<li> Severity: Error </li>

<li> Explanation: The  domain attribute&#x27;s value,  (for MTA purposes, the value of whatever attribute is named by the     MTA option), does not parse properly as a DN. </li>

<li> User Action: Check for syntax errors in the value of. </li>

</ul> %DMAP-E-INVALIDDEFMAILHOST, Default mailHost &#x27;host-string&#x27; for domain &#x27;domain-name&#x27; is invalid <ul>

<li> Facility: </li>

<li> Severity: Error </li>

<li> Explanation: The domain LDAP attribute named by the    MTA option (not set by default) is set to a value which is not a syntactically valid domain name. </li>

<li> User Action: Specify a syntactically valid (and, one hopes, semantically correct) domain name as the value. </li>

</ul> %DMAP-W-INVALIDDOMSTAT, Domain status &#x27;status&#x27; for domain &#x27;domain-name&#x27; base node at DN-string is invalid <ul>

<li> Facility: </li>

<li> Severity: Warning </li>

<li> Explanation: Schema 2. The   value (for MTA purposes, the value of  whatever attribute is named by   )  was not valid:  it was something other than ,  ,  or. Processing will continue after this warning. </li>

<li> User Action: If this is a domain intended for mail use by the MTA, set a valid value for  ;  however, if this domain is not going to be used for mail purposes, this  warning may not be of concern. (Note that "switching" of the meaning of   and    is supported by the MTA, by  "switching" the values of    and  , with the attribute named by   , normally   , allowing additional supported  values. So other than a simply outright "wrong" value for   , another possibility is that the meanings  and hence values were "switched" in a prior configuration.) </li>

</ul> %DMAP-W-INVALIDUIDSEP, Domain &#x27;domain-name&#x27; has an empty UID separator attribute <ul>

<li> Facility: </li>

<li> Severity: Warning </li>

<li> Explanation: The   domain attribute  (or more precisely, the LDAP attribute named by the   MTA option) is set to a value containing invalid characters. </li>

<li> User Action: Set a valid value. Note that while the MTA doesn&#x27;t directly use the value, the authentication library code  does make use of the attribute&#x27;s value. </li>

</ul> %DMAP-W-MULTDOMAINNAMES, Domain entry with DN &#x27;DN-string&#x27; has multiple domain names, used value &#x27;name-1&#x27; ignored &#x27;name-2&#x27; <ul>

<li> Facility: </li>

<li> Severity: Warning </li>

<li> Explanation: The domain entry has multiple values of the   LDAP attribute (or for the MTA,  more precisely whatever LDAP attribute is named by the     MTA option). Processing will continue---but this is presumably a provisioning error. </li>

<li> User Action: Remove the extraneous   values. </li>

</ul> %DMAP-W-MULTIAPPSTAT, Multivalued application status in entry for domain &#x27;domain-name&#x27;, used value &#x27;first-found&#x27; ignored &#x27;later-found&#x27; <ul>

<li> Facility: </li>

<li> Severity: Warning </li>

<li> Explanation: The   domain attribute (or more precisely, the LDAP domain attribute named by the   MTA option) has multiple values set. </li>

<li> User Action: Remove the extraneous values: this should be a single-valued attribute. Note that as LDAP leaves unspecified the order in which values are returned, having multiple values set will result in unpredictable/unreliable results. </li>

</ul> %DMAP-W-MULTIBASEDN, Multivalued base DN pointer in entry for domain &#x27;domain-name&#x27;, used value &#x27;DN-string-1&#x27; ignored &#x27;DN-string-2&#x27; <ul>

<li> Facility: </li>

<li> Severity: Warning </li>

<li> Explanation: The domain entry has two (or more)   values (or for the MTA, more precisely  multiple values of whatever LDAP attribute is named by the     MTA option). Processing continues, but a warning is issued since this is presumably a provisioning error. </li>

<li> User Action: Remove all but one   value, as only one value will be used. Note that if user/group entries for the domain are currently scattered under multiple locations in the DIT, attempting to set multiple    values to point to those multiple  locations will not work---instead, one    must be specified above all the user/group entries for the  domain, restructing the DIT if necessary to achieve this. </li>

</ul> %DMAP-E-MULTICANONICAL, Multivalued canonical name in entry for domain &#x27;domain-name&#x27;, used value &#x27;first-found&#x27; ignored &#x27;later-found&#x27; <ul>

<li> Facility: </li>

<li> Severity: Error </li>

<li> Explanation: The   domain attribute (or more precisely, the LDAP domain attribute named by the   MTA option) has multiple values set. </li>

<li> User Action: It is a provisioning error to have multiple canonical domain names set: remove the extraneous value(s). Note that the LDAP specification does not define which value will be returned "first", and indeed the order may vary from LDAP query to LDAP query. So although processing will continue after such an error, the resulting effect during operation may be unreliable, if varying canonical names are returned. </li>

</ul> %DMAP-E-MULTIDEFMAILHOST, Multivalued mailhost default in entry for domain &#x27;domain-name&#x27;, used value &#x27;value-0&#x27; ignored &#x27;value-1&#x27; <ul>

<li> Facility: </li>

<li> Severity: Error </li>

<li> Explanation: The domain LDAP attribute named by the    MTA option (not set by default) has multiple values set. </li>

<li> User Action: Remove the extraneous values. </li>

</ul> %DMAP-W-MULTIDOMSTAT, Multivalued domain status in entry for domain &#x27;domain-name&#x27; base node at DN-string, used value &#x27;status-0&#x27; ignored &#x27;status-1&#x27; <ul>

<li> Facility: </li>

<li> Severity: Warning </li>

<li> Explanation: Schema 2. Multiple   values (for MTA purposes, multiple values  for whatever attribute is named by   )  were found. Processing will continue after this warning, with whatever value LDAP happened to return first being used. </li>

<li> User Action: Remove all but one (correct) value for. </li>

</ul> %DMAP-W-MULTIUIDSEP, Multivalued UID separator in entry for domain &#x27;domain-name&#x27;, used value &#x27;value-0&#x27; ignored &#x27;value-1&#x27; <ul>

<li> Facility: </li>

<li> Severity: Warning </li>

<li> Explanation: The   domain attribute  (or more precisely, the LDAP attribute named by the   MTA option) has multiple values. </li>

<li> User Action: Remove the extraneous values. Recall that as LDAP makes no guarantees regarding the order in which values are returned, having multiple values can lead to unpredictable/unreliable results. Note that while the MTA doesn&#x27;t directly use the value, the authentication library code  does make use of the attribute&#x27;s value. </li>

</ul> %DMAP-W-MULTIVALIAS, Multivalued alias pointer in entry for domain alias &#x27;domain-name&#x27;, used value &#x27;DN-string-0&#x27;, ignored &#x27;DN-string-x&#x27; <ul>

<li> Facility: </li>

<li> Severity: Warning </li>

<li> Explanation: The supposed domain alias entry has multiple values of the   LDAP attribute  (in the case of the MTA, more precisely, multiple values for whatever  LDAP attribute is named by the     MTA option). All values other than the "first" that happened to be reported on  this LDAP query will be ignored---but recall that LDAP makes no  guarantee as to the order in which attributes are returned, so such  ordering and hence which value is used may vary between different  queries! Since getting inconsistent effects, varying with the order in which the LDAP directory happened to return results, is unlikely to be  desirable, this is a warning of what can be presumed to be a  provisioning error, though processing will continue using the  "first" value reported by LDAP. </li>

<li> User Action: Remove all the redundant or extraneous   values, so that only the one correct  value remains in the domain alias entry, and so that consistent  processing will occur. </li>

</ul> %DMAP-E-NOBASEDN, Domain &#x27;domain-name&#x27; has no base DN <ul>

<li> Facility: </li>

<li> Severity: Error </li>

<li> Explanation: Schema 1. This domain entry has no explicit , (or for the MTA, more precisely  whatever LDAP attribute is named by the    MTA  option); such an attribute is required in Schema 1. </li>

<li> User Action: Add an   attribute specifying where users/groups in this domain are stored in  the DIT. </li>

</ul> %DMAP-E-NOBASEDN, Domain &#x27;domain-name&#x27; has an empty base DN <ul>

<li> Facility: </li>

<li> Severity: Error </li>

<li> Explanation: Schema 1 or Schema 2. This domain entry has an   LDAP attribute, (or for the MTA,  more precisely whatever LDAP attribute is named by the     MTA option) with no value set. </li>

<li> User Action: Specify a value for the   LDAP attribute specifying where  users/groups in this domain are stored in the DIT; or in Schema 2  only another alternative is to remove the    attribute entirely, to indicate that  users and groups in this domain will be located directly under this  domain entry in the DIT. </li>

</ul> %DMAP-W-NOBASEDNNODE, Base DN pointer &#x27;DN-string&#x27; in entry for domain &#x27;domain-name&#x27; doesn&#x27;t point at anything <ul>

<li> Facility: </li>

<li> Severity: Warning </li>

<li> Explanation: The  value  (for the MTA, more precisely the value of whatever attribute is named  by the     MTA option) corresponds to no actual  node in the directory. Processing will continue after this warning. </li>

<li> User Action: If the domain in question is intended for current use, then this is a warning of some form of provisioning error:  either the   value is incorrect, or the  data supposed to be in the directory is missing or in the  "wrong" location. However, if this is a "place-holder" domain entry intended for later use, but not  yet fully provisioned (in particular not yet provisioned with any  users), then this warning may not be of concern at this time. Decide whether the domain in question is intended for current use, and if so,  ensure that its   value points to the  intended base DN under which its users are, or will be, located. </li>

</ul> %DMAP-E-NODOMAINNAME, Domain entry with DN &#x27;DN-string&#x27; does not have a domain name <ul>

<li> Facility: </li>

<li> Severity: Error </li>

<li> Explanation: Schema 2. The domain entry does not have a   LDAP attribute (or for the MTA, more  precisely whatever LDAP attribute is named by the     MTA option). </li>

<li> User Action: Add the domain name to the entry; that is, add a   LDAP attribute specifying the  desired domain name. </li>

</ul> %DMAP-W-NODOMAINNAME, Domain entry with DN &#x27;DN-string&#x27; has a blank domain alias <ul>

<li> Facility: </li>

<li> Severity: Warning </li>

<li> Explanation: Schema 2. The domain entry has a   LDAP attribute (or for the MTA, more  precisely whatever LDAP attribute is named by the     MTA option) with no value. Processing continues, but a warning is issued since this is presumably a  provisioning error. </li>

<li> User Action: Either set a valid value in , or remove the attribute. </li>

</ul> %DMAP-W-NOENTRIES, No domain entries found, aborting <ul>

<li> Facility: </li>

<li> Severity: Warning </li>

<li> Explanation: No domain entries were found. </li>

<li> User Action: This is the expected output if pointing to an LDAP directory that does not contain Schema 1 or Schema 2 compatible domain entries. However, if the MTA has been configured to consult an LDAP directory that does (supposedly) contain valid domain entries, then something is wrong with basic configuration: e.g., MTA configuration for what LDAP directory to consult is incorrect, or the MTA cannot see the domain entries  (authentication problems, or ACLs preventing access), or the MTA has not been configured properly for where in the DIT to look to find domain entries. </li>

</ul> %DMAP-W-SHORTFORMDEFMAILHOST, Default mailHost &#x27;host-string&#x27; for domain &#x27;domain-name&#x27; is a shortform name <ul>

<li> Facility: </li>

<li> Severity: Warning </li>

<li> Explanation: The domain LDAP attribute named by the    MTA option (not set by default) is set to a short form hostname value, rather than to a fully qualified domain name. </li>

<li> User Action: Use of fully qualified domain names is strongly recommended: change value to be in fully qualified form. </li>

</ul> %DMAP-W-SHORTFORMDOMAIN, Short form domain name &#x27;domain-name&#x27; defined/referenced by domain entry with DN &#x27;DN-string&#x27; <ul>

<li> Facility: </li>

<li> Severity: Warning </li>

<li> Explanation: The domain name (whether constructed from the " " chunks in the   in Schema 1 mode, or found in the   attribute in Schema 2 mode) is a "short form" host name, rather than a fully qualified domain name. </li>

<li> User Action: Use of fully qualified domain names is strongly recommended; strongly consider revisiting domain name usage and switching to use of fully qualified domain names. </li>

</ul> %DMAP-W-SHORTFORMDOMAINALIAS, Short form domain alias &#x27;string&#x27; is defined/referenced by domain entry with DN &#x27;DN-string&#x27; <ul>

<li> Facility: </li>

<li> Severity: Warning </li>

<li> Explanation: A domain alias has been specified in "short form" host name form, rather than as aa fully qualified domain name. </li>

<li> User Action: Use of fully qualified domain names is strongly recommended; strongly consider revisiting domain name usage and switching to use of fully qualified domain names. </li>

</ul>

See also:
 * Base domainmap options
 * usedomainmap Option
 * Overview of Direct LDAP configuration
 * MTA command line utilities