From owner-freebsd-isp  Thu Mar  4  1:55:21 1999
Delivered-To: freebsd-isp@freebsd.org
Received: from titan.eclipse.co.uk (titan.eclipse.co.uk [195.188.32.18])
	by hub.freebsd.org (Postfix) with ESMTP id 40C7B15056
	for <freebsd-isp@FreeBSD.ORG>; Thu,  4 Mar 1999 01:54:45 -0800 (PST)
	(envelope-from stuart@eclipse.net.uk)
Received: from eclipse.net.uk ([195.188.32.31]) by titan.eclipse.co.uk
          (Netscape Messaging Server 3.5)  with ESMTP id AAAAB1;
          Thu, 4 Mar 1999 09:54:25 +0000
Message-ID: <36DE58A9.E048B6EA@eclipse.net.uk>
Date: Thu, 04 Mar 1999 09:55:53 +0000
From: Stuart Henderson <stuart@eclipse.net.uk>
Organization: Eclipse Networking Ltd.
X-Mailer: Mozilla 4.5 [en] (WinNT; U)
X-Accept-Language: en-GB
MIME-Version: 1.0
To: Andrew McNaughton <andrew@squiz.co.nz>
Cc: Haifeng Guo <haifeng@ms.lawton.com.cn>, freebsd-isp@FreeBSD.ORG
Subject: Re: Mail server setup
References: <199903040638.TAA02409@aniwa.sky>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-isp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> I don't imagine you really want to have to organise 100,000 
> users into changing their pop server settings.  You can 
> probably multiplex your domain name out to multiple machines 
> all connecting via NFS (probably a dedicated mini-network 
> between the servers), and have all of your mail stored on 
> one file system.

You could have a daemon on a cluster of machines (either DNS or
NAT-based load balancing) to answer port 110, examine the username to
choose a server and proxy off the connection. Aren't NFS mounted mail
spools generally a Bad Thing?


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message