From owner-freebsd-isp Wed Mar 10 23: 8:46 1999 Delivered-To: freebsd-isp@freebsd.org Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (Postfix) with ESMTP id 109BE1502D for ; Wed, 10 Mar 1999 23:08:21 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.9.1/8.8.7) with ESMTP id CAA72568; Thu, 11 Mar 1999 02:07:32 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: "Kurt Jaeger" Cc: stuart@eclipse.net.uk (Stuart Henderson), andrew@squiz.co.nz (Andrew McNaughton), haifeng@ms.lawton.com.cn (Haifeng Guo), freebsd-isp@FreeBSD.ORG From: "Gary Palmer" Subject: Re: Mail server setup In-reply-to: Your message of "Thu, 04 Mar 1999 13:33:17 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Mar 1999 02:07:32 -0500 Message-ID: <72564.921136052@gjp.erols.com> Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kurt Jaeger" wrote in message ID : > Depends on the setup. No, it doesn't. NFS is not the best idea for any system which does hundreds or thousands of directory lookups per second with little or no file i/o in comparison. If you think about it for a second, a mail system is just that (in general). You get a lot of people checking mail, and only a few of those have (new) mail and download it. This makes NFS a serious pain in the rear (since it can't really do directory caching). If you ended up doing a lot of I/O, you'd probably want to be looking at CDDI or FDDI for NFS also, to cut down on the number of packets and/or fragments flying around (depending on how you set it up). > Have a look at: > > http://www.earthlink.net/company/mail_arch.html > > It describes their e-mail architecture for quite a large user community. I've often wondered what kick-back they get from NetApp for publishing that There are other alternatives to NFS. Doing POP3 & SMTP proxying makes a lot more sense IMNSHO. You basically end up with a set of front-end machines which do username lookups and route incoming traffic to the appropriate backend. The system is highly scalable. You just add more machines. By my guess, you'd have to go well past 1m users to max out full duplex fast ethernet in this setup. Past posts on this from any number of ppl (mostly me tho :) ) should be in the archives. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message