Multi Verifier Example 1

The following Multi verifier contains two LDAP sub-verifiers, each one with a primary and backup server, and a list of BaseDNs to search. Both use default queries for Active Directory servers.

In this Multi verifier, the search request will first be sent to host 216.141.147.111 (or 216.141.147.110 if 216.141.147.111 is unavailable). If a match is found, the result is that the email address is verified. No further search is performed.

If no match is found, then host 216.141.147.113 (or 216.141.147.112 if .113 is unavailable) is tried. Only if this query also fails will the address be reported as not verified. Both of the sub-verifiers will be enumerated, on-average, every 50 minutes.

Because this Multi verifier does not contain an <InterDiscTime> element, the Multi verifier is unaware of which domains are serviced by each sub-verifier and all searches will try the first sub-verifier. If there is no match, it searches the second sub-verifier. If any sub-verifier has an error, the verification query returns an error.

<Vrfy name="ben``"

uid="64378E3C-A459-11DD-1273-09173F13E4C5"

version="101.4635">

<Multi>

<Username>Red Condor</Username>

</Credentials>

<BaseDN>OU=ADC Staging,DC=ben,DC=pri</BaseDN>

<BaseDN>OU=Adjunct Faculty,DC=ben,DC=pri</BaseDN>

<BaseDN>OU=BEN Faculty,DC=ben,DC=pri</BaseDN>

<BaseDN>OU=BEN Staff,DC=ben,DC=pri</BaseDN>

<BaseDN>OU=BEN Technical,DC=ben,DC=pri</BaseDN>

<BaseDN>OU=Service Accounts,DC=ben,DC=pri</BaseDN>

<BaseDN>OU=Student Workers,DC=ben,DC=pri</BaseDN>

<BaseDN>CN=Users,DC=ben,DC=pri</BaseDN>

<BaseDN>CN=Microsoft Exchange System Objects,DC=ben,DC=pri</BaseDN>

</LDAP>

<Username>Red Condor</Username>

</Credentials>

<BaseDN>OU=ActiveStudents,DC=stuben,DC=ben,DC=edu</BaseDN>

<BaseDN>OU=NewStudents,DC=stuben,DC=ben,DC=edu</BaseDN>

<BaseDN>CN=Microsoft Exchange System Objects,DC=stuben,DC=ben,DC=edu</BaseDN>

</LDAP>

</Multi>

</Vrfy>