From owner-freebsd-chat Fri Feb 14 11: 4:42 2003 Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C998637B401 for ; Fri, 14 Feb 2003 11:04:40 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id B669443FBF for ; Fri, 14 Feb 2003 11:04:39 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0241.cvx22-bradley.dialup.earthlink.net ([209.179.198.241] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18jl8T-0004Se-00; Fri, 14 Feb 2003 11:04:34 -0800 Message-ID: <3E4D3D70.266DB2E4@mindspring.com> Date: Fri, 14 Feb 2003 11:03:12 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Brad Knowles Cc: Rahul Siddharthan , freebsd-chat@freebsd.org Subject: Re: Email push and pull (was Re: matthew dillon) References: <20030211032932.GA1253@papagena.rockefeller.edu> <3E498175.295FC389@mindspring.com> <3E49C434.D8D497EE@mindspring.com> <3E4A83BC.8A15E7C3@mindspring.com> <3E4B12F5.2608BBB@mindspring.com> <3E4BB64E.A9AEED28@mindspring.com> <3E4C9612.2777D62E@mindspring.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4ecdef25142ca04a22fb62899028c08c093caf27dac41a8fd350badd9bab72f9c350badd9bab72f9c Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Brad Knowles wrote: > At 11:09 PM -0800 2003/02/13, Terry Lambert wrote: > > No... but does proxy really solve anything, then, more than > > a DNS rotor solves? All it really does is add a single point > > of failure. Unless you can target a subset of back end content > > servers, you might as well use DNS round-robin. Using a proxy > > implies the back end replica problem is *already* solved. > > Yes, the proxy does solve the domain problem. The user logs in > with "user@domain", the proxy looks this up in the LDAP database, > which then tells it which back-end server to contact. You can > decide, on a user-by-user basis, which back-end server they will be > using for their mail. If one back-end server gets overloaded, you > can choose individual users to shift off to another machine. I solved this particular problem by modifying Cyrus to know about domains. But the point was kind of that there are IMAP4 clients that strip "@.*" off logins, if they have "@" in them. > > Maybe I should say "doesn't deal with LDAP the way it should" > > instead? > > In what way? The LDAP should be used to determine the set of back end servers, not to strip the domain name, and use it to pick a domain-specific back end server. The reason this is true should be obvious: if it doesn't, then the number of domains you can support is limited to, at most, the number of back end servers. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message