From owner-freebsd-isp@FreeBSD.ORG Wed Oct 13 00:38:59 2004 Return-Path: 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 3801B16A4CE for ; Wed, 13 Oct 2004 00:38:59 +0000 (GMT) Received: from gak.upnix.net (gak.upnix.net [216.194.85.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFC6743D3F for ; Wed, 13 Oct 2004 00:38:58 +0000 (GMT) (envelope-from chris@upnix.com) Received: from bawls.upnix.net ([209.82.103.246]) (authenticated bits=0) by gak.upnix.net (8.12.11/8.12.11) with ESMTP id i9D0cvWP002117 for ; Tue, 12 Oct 2004 18:38:57 -0600 (MDT) From: Chris Cameron Organization: UpNIX Internet To: freebsd-isp@freebsd.org Date: Tue, 12 Oct 2004 18:39:16 -0600 User-Agent: KMail/1.6.2 References: <20041012212051.5A91A148D1@mail.sources.org> In-Reply-To: <20041012212051.5A91A148D1@mail.sources.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <200410121839.16513.chris@upnix.com> Subject: Re: Documentation of big "mail systems"? X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Oct 2004 00:38:59 -0000 http://www.gangofone.com/~npc/doc/mail_arch.html It's -old-, but I had it handy. On October 12, 2004 03:20 pm, Stephane Bortzmeyer wrote: > I'm currently writing a proposal for a webmail service for, say, 50 > 000 to 500 000 users. I'm looking for description of existing "big > mail" systems, using technologies like scalemail > (http://scalemail.sourceforge.net/), specially with an emphasis on > the storage subsystem for the servers (my weak point, I don't really > have enough experience with SAN, NAS, and so on). > > Of course, with a FreeBSD (and free software) bias :-) > > I do not need general advice (such as "Postfix rules, Exim sucks" or > "Maildirs are faster") but actual description of existing and running > systems. Googling seems inefficient for that purpose and I presume > that many interesting papers are only in closed and paying conference > proceedings :-(