Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Stop mail from bouncing



On Aug 31, 2005, at 9:45 AM, Matthew Gillen wrote:

> Josh ChaitinPollak wrote:
>
>> We recently split the ldap and mail servers onto two separate  
>> boxes  to
>> make them more reliable, but this seems to have only caused more
>> problems. Should I be mirroring the ldap config on the mail server?
>>
>
> You should have a slave LDAP server *somewhere*.  Not being able to  
> look
> up user info causes so many problems that every  major network user- 
> info
> system (NIS, LDAP, Active Directory, etc) has explicit support for
> slave/secondary servers.

How do our client applications and daemons figure out when and where  
to connect to the slave ldap server? Most applications I've seen only  
have entries for a primary server..





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org