Domino LDAP Issues When Full Text Indexing Names.nsf
We have been using Ironport for over three years now and have finally decided to tie it in with our Domino LDAP. Unfortunately, over the years we have been lenient with our mail policies and users have gotten used to using a number of email address variations. To capture these, we are searching on the following:
"mail" is their normal address; "email" is an alternate for people who have had a name change due to divorce, marriage, etc.; "cn" is first initial-last name, and "uid" is last name-first initial.
This works fine using LDAP Browser, the Ironport LDAP tester, and a few limited-time live implementations. However, it is quite slow: 4-5 seconds per lookup. Taking the advice of someone in another post on this message board, we full text indexed our names.nsf file. The results were much faster, generally under a second.
However, the results also became more erratic. Though we didn't change our query string, we were now getting query failures when entering email@example.com (our standard address - the "mail" field). This only happens to users who don't have an "email" field in LDAP. If they have "mail" and "email" then the results come back positive.
Has anyone experienced this before while using Domino LDAP? I would hate to abandon full text indexing as it speeds the lookups considerably.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...