From owner-freebsd-isp@FreeBSD.ORG Fri Jul 7 03:24:57 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C28B16A4DD for ; Fri, 7 Jul 2006 03:24:57 +0000 (UTC) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FBC243D4C for ; Fri, 7 Jul 2006 03:24:56 +0000 (GMT) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (localhost.natserv.net [127.0.0.1]) by zoraida.natserv.net (Postfix) with ESMTP id 14482B833; Thu, 6 Jul 2006 23:24:54 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on zoraida.natserv.net X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed version=3.1.3 Received: from zoraida.natserv.net (zoraida.natserv.net [66.114.65.147]) by zoraida.natserv.net (Postfix) with ESMTP id C17CCB822; Thu, 6 Jul 2006 23:24:53 -0400 (EDT) References: <20060706235712.A1171@ganymede.hub.org> Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Francisco Reyes To: User Freebsd Date: Thu, 06 Jul 2006 23:24:53 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: FreeBSD ISP Subject: Re: IAMP servers in FreeBSD for ISP X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 03:24:57 -0000 User Freebsd writes: > If I recall your environment at all, one nice feature of it is that it > supports something called MURDER, which, effectively, is a way of having > your mailboxes literally spread out over multiple backend servers ... > all the mail comes in through ServerA, but, as an example, mailboxes a-m > get stored on ServerB, and n-z go to ServerC ... What happens if Server A dies? > They've also just recently added a replication ability, so that you can > have backup servers ... ServerD is a backup of ServerB, ServerE is a > backup of ServerC ... These backup servers are they for what you call A above or the storage machines? > The thing is, it would most likely eliminate, or greatly reduce, your NFS > requirements ... Now that you mention they have replication, it definitely is worth re-looking at it. I inheritted courier and at the time we were not growing as fast as we are now.. We used to get smaller accounts so the increase in load was always fairly small and we could extremely easily plan adding more capacity. Now that we have larger orders coming in it's a whole different game.. Eliminating NFS will be one great added bonus.. Will read up on Cyrus.. This replication feature, is it brand new or has it been been tested well by now?