From owner-freebsd-isp  Thu Sep 16 10:35:11 1999
Delivered-To: freebsd-isp@freebsd.org
Received: from proteus.eclipse.net.uk (proteus.eclipse.net.uk [195.188.32.118])
	by hub.freebsd.org (Postfix) with ESMTP id 1682114F6F
	for <freebsd-isp@FreeBSD.ORG>; Thu, 16 Sep 1999 10:35:01 -0700 (PDT)
	(envelope-from stuart@eclipse.net.uk)
Received: from eclipse.net.uk (elara.eclipse.net.uk [195.188.32.31])
	by proteus.eclipse.net.uk (Postfix) with ESMTP
	id 53A729B18; Thu, 16 Sep 1999 18:34:57 +0100 (BST)
Message-ID: <37E12AF1.23354261@eclipse.net.uk>
Date: Thu, 16 Sep 1999 18:37:53 +0100
From: Stuart Henderson <stuart@eclipse.net.uk>
Organization: Eclipse Networking Ltd.
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en-GB
MIME-Version: 1.0
To: Fernando Schapachnik <fpscha@via-net-works.net.ar>
Cc: freebsd-isp@FreeBSD.ORG
Subject: Re: SMTP load balancing
References: <199909151338.KAA15642@ns1.sminter.com.ar>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-isp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> a) The front end still has to manage the huge amount of incoming mail.

With something like ldap or SQL (or hash the username to work out which
box should store the mail) you can have X number of frontends with 
identical configuration delivering to the backend boxes. If it's
ldap then replication of database servers is reasonably simple too.

> b) Uniform POP3 access to mailboxes under the same name becomes imposible.

Modify Perdtion as per requirements.


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