From owner-freebsd-isp Fri Jul 27 4:19:32 2001 Delivered-To: freebsd-isp@freebsd.org Received: from mail.plug.cx (kypo.alfred.cx [150.101.93.134]) by hub.freebsd.org (Postfix) with ESMTP id 67CDB37B406 for ; Fri, 27 Jul 2001 04:19:25 -0700 (PDT) (envelope-from andrew.reid@plug.cx) Received: from [210.11.50.146] (unknown [210.11.50.146]) by mail.plug.cx (Postfix) with ESMTP id 9BBC92B7ED; Sat, 28 Jul 2001 06:41:06 +0930 (CST) Subject: Re: FreeBSD Mail Toaster CLUSTER From: Andrew Reid To: so@server.i-clue.de Cc: Fabrizio Ravazzini , freebsd-isp@FreeBSD.ORG In-Reply-To: <3B5FDE77.DC5FC3DB@i-clue.de> References: <20010726065304.39908.qmail@web20106.mail.yahoo.com> <3B5FDE77.DC5FC3DB@i-clue.de> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <996207686.1405.14.camel@percible.alfred.cx> Mime-Version: 1.0 X-Mailer: Evolution/0.11 (Beta Release) Date: 27 Jul 2001 17:16:21 +0930 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 26 Jul 2001 11:10:15 +0200, Christoph Sold wrote: > As DNS & bind tells, just have two mail servers accept SMTP for your > domain. Assign different names and A records, as well as set both as MX > for your domain. > > If one goes down, the other will get the mail automatically. I've been thinking about putting in another mailserver for redundancy. The notion of setting up a secondary MX host is easy enough, but it doesn't seem to be enough for what I'd like to do. For example: +-----------------------+ +---------+ | |---------------->| MX1 | | Load Balancing Device | +---------+ | | +---------+ | |---------------->| MX2 | +-----------------------+ +---------+ If the Load Balancing Device ("LBD") is sharing out connections for ports 25 and 110 between MX1 and MX2, I want to be sure that if one of the two machines goes down, everyone can still get their mail. I've looked at some methods of doing this where, when accounts are created, they are equally dispersed amongst your MX farm, but that means that all users on the dead MX will have no mail access. How are people going about delivering distributed, redundant, load-balanced mail? I was thinking that some form of parallel delivery could be implemented, but that would result in the load of MX1 and MX2 being pretty similar (one would think). You don't want to have all your eggs in one basket, but at the same time, you do. You want to be able to get to your mail -all- the time, not just when the appropriate server is up. If accounts "joe", "thelma" and "louise" are on MX1, they still need to be able to get to their mail, even when the server is down. Hmm! Suggestions? - andrew -- void signature () { cout << "Andrew Reid -- andrew.reid@plug.cx" << endl ; cout << "Cell: +61 401 946 813" << endl; cout << "Quidquid latine dictum sit, altum viditur" << endl; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message