Graziano, You have been asking questions for some time about LDAP. I'm not sure if anyone has mentioned that LDAP is only one of several possible ways to authenticate users. In my understanding, alternatives include: -
1 Authentication by the MTA itself - the best and simplest alternative in most cases? 2 Flat file with specific usernames ([EMAIL PROTECTED]), i.e. authenticated by ASSP. Simple but tedious to update. Most easily done with a script to extract the addresses from a list somewhere else 3 Flat file with wildcard domain names (@domain1.tld) , i.e. "authenticated" by ASSP. Quick and easy, but has the problem that too many undeliverable messages might be received for non-existent addresses. 4` LDAP as a mechanism to interface to either a database or an MTA, i.e. authenticated via some third party mechanism, with LDAP as an interface. Updating becomes the problem of the 3rd party application. An example is the internal Windows User DB (Active Directory). LDAP interfacing is included in Windows Active Directory from W2K onwards. More accurately, AD is a "native" LDAP server, they say. You only need LDAP if you can't do any of the first three. From what little I know of LDAP, it's quite a complex subject to address from scratch, but not THAT hard. It's relatively easy to interface to some existing LDAP server. Google! Kind regards, William Stucke ZAnet Internet Services (Pty) Ltd [EMAIL PROTECTED] 083-308-0700 - WFS 074-333-0109 - Office 086-502-9444 - Fax http://www.zanet.co.za ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
