Edward Wildgoose wrote: > > I am at the planning stage of an LDAP deployment, having user > accounts, PAM, Courier IMAP, Postnuke and Postfix authentication via > LDAP > > I would be really keen to hear a basic overview of the issues involved > in planning this, and where to go for further info. For example where > to go to find out about Schemas required, how to plan a domain layout > (I have one machine supporting two mail domains...). This is only > going to support a few users, but might grow to multiple machines at > some point
Well' it all depends on what you want. Often, it is wise to determine what information is a) unlikely to change b) representing your system For example, if the users on your system will always be receiving mail for only one of the domains, it might be wise to create a branch for each domain, and create a branch for the users below those. If a user may receive mail for addresses under both domains, or none, you should's seperate them per domain. The same thing you can think of when decideing about types of users. In our own systems, we usually split up real unix users from mail or ftp users. That is to make sure unix users (which are required to login with ssh) will not use the same password or account as the use for insecure pop3 or ftp sessions. In this case we have two branches, one for 'real' users, one for virtual users. What we generally do with users for proftpd, is to link them to a dns domain, determine their homedirectory from that domain name, and have apache automatically determine their homedirectory and website from it.. i'll post some example entries soon.. Regards, rolek -- 1A First Alternative [EMAIL PROTECTED] www.alt001.com Linvision BV [EMAIL PROTECTED] (www|devel).linvision.com -- _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
