We run NFS here on 4 servers without issue. We have yet to have any of our servers fail because of NFS.
The variable basedn works to speed up the lookup. Especially if you have designed your LDAP tree on location or organization. In our case we have other domains and it really makes no since to search the entire tree for a listing that the system can find 10 times faster by using the information of the login or smtp session. Also it allows you to put multiple entries that are the same. i.e. [EMAIL PROTECTED] and [EMAIL PROTECTED] can have the same pop login with a variable dn but cannot with the current system. If I knew how to write it I would write the code myself. But alas I do not. -----Original Message----- From: Kosh Naranek [mailto:[EMAIL PROTECTED]] Sent: Monday, March 11, 2002 10:07 PM To: [EMAIL PROTECTED] Subject: RE: high availability solution? NFS is too unreliable though, I've used it on simple backup runs and it had so many problems. Some kind of specifically designed for qmail-ldap striping system would work perfectly, but that is reinventing the wheel to add a new hubcap :) -----Original Message----- From: Gene Parks [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 12 March 2002 07:01 To: [EMAIL PROTECTED] Subject: RE: high availability solution? If you had a common storage area i.e. a NAS then you could just bring the second server online mount the NFS and add the mx record. This would accomplish what you are looking for since when you take one out of service the other mail server trying to send mail will use the second record. And since the mail is local to all boxes then you do not have to worry about the mailhost attribute or clustering. -----Original Message----- From: manfred [mailto:[EMAIL PROTECTED]] Sent: Monday, March 11, 2002 6:52 AM To: [EMAIL PROTECTED] Subject: high availability solution? Hi everybody, I have a little understanding question to qmail-ldap. I haven't found an answer to this in the documentation yet, so I'll give it a try here. I'm running qmail-ldap without clustering enabled and it works really nice. Now I want to have a second server installed for the case, that the main server has to be maintained or is going down. As I understand (please help me if I'm wrong here which I certanly might), qmail-ldap has clustering support which is designed for load-balancing in the first place. So, when cluster-members receive pop3 sessions, they try to hand it over to the mailHost cluster-Server, right? But what, if this one is down? Does the session end with an error for the pop user? I assume, that smtp sessions (local delivery) will work and the cluster-member tries to connect to the mailHost cluster when it's up again to sync the maildirs, or am I wrong? So another way would be, to have a second MX entry, which would be fine for 'hot-standby' of the second server, but let's assume the case, that a lot of mails get handled locally in the time, the first server is down. Then, how is it possible to have the mails delivered from the second server to the first, so the maildirs of the first server have all the mails (because ongoing pop sessions will be handled by the first MX again)? I would really appreciate some hints on this topic, maybe a good starting point in the web for further research, befor I try to configure 'something'. Thanks a lot. Manfred
