IIS 6: The Complete Reference

Configuring Lightweight Directory Access Protocol (LDAP) routing will enable the SMTP virtual server to obtain settings in an LDAP to resolve senders and recipients. If groups are already established in the LDAP, likely due to the fact the LDAP is being used for other user management efforts, the e-mail addresses may be extracted from these preexisting groups and expanded by SMTP when the group name is cited in a message.

To configure an SMTP virtual server, the Computer Management MMC snap-in will be used to obtain the Properties windows for the respective SMTP virtual server. All the settings for configuring LDAP routing are located under the LDAP Routing tab of the Properties window.

On the LDAP Routing tab, the only control that is enabled is the Enable LDAP Routing checkbox. If the Enable LDAP Routing checkbox is not checked, none of the configurations will be enabled. By default, Enable LDAP Routing is not checked. After the Enable LDAP checkbox is checked, the following configurations become enabled and may be set:

• Server Name of the server hosting the LDAP server. If Exchange LDAP is selected, this setting is not applicable since the Exchange server will be found through self discovery by the host automatically.

• Schema The type of LDAP that will be utilized. Active Directory, Exchange, and Site Server are the LDAP types that may be chosen.

• Binding The type of authentication that will be used to connect to the directory.

• Base The distinguished name of a container that represents the starting point for a search in the directory.

If a binding other than anonymous or service account is chosen, the username, password, and domain configurations are made available because these bindings require credentials for authentication to be specified. In the case of service account, the credentials of the user connecting to the SMTP server are sent for authentication to the LDAP. The username credentials should be specified in the distinguished name (DN) format. For example, the DN of a user with the username jschmidlap working for the beer brewer's organization in the Schmitt House company might appear as follows:

cn=jschmidlap,ou=beerbrewer,o=SchmittHouse