> What we really need is a function like 'SetDomain' where we can > rewrite the storing of the information from the registry to LDAP.
As someone who has written several custom userbase DLLs, including an LDAP interface, I can assure you that you DO NOT want to store any more data in LDAP than is actually necessary. LDAP is not a configuration management protocol and is ill-suited to the query frequency and traffic volume of a userbase-only implementation--let alone trying to add hostbase information to the mix. If performance is of any importance at all, you will find yourself wanting to reduce and/or short-circuit your LDAP queries, not add *more* overhead. You are correct, of course, that IMail uses Registry hostbase data as the "anchor" for userbase DLLs, regardless of where userbase data is stored. While flexibility there might be nice, the design is quite sensible, given the read-mostly nature of hostbase data and the tremendous read volume on that data. The only practical way to create an LDAP "master" for hostbase data is to overwrite the Registry settings from LDAP just once, at service start, then do not touch that LDAP area again. Believe me, as you see the performance issues we wrangle with constantly--the cause, I should mention, for my constant reminders that the Registry database is hundreds of times more efficient than most external interfaces--you'll reconsider this part of your design. -Sandy To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
