From owner-freebsd-questions  Wed Jun  7  6:51:12 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from mail2.wmptl.com (mail2.wmptl.com [216.221.73.131])
	by hub.freebsd.org (Postfix) with ESMTP id 49EF237BCDC
	for <questions@freebsd.org>; Wed,  7 Jun 2000 06:51:06 -0700 (PDT)
	(envelope-from webmaster@wmptl.com)
Received: from wmptl.com ([10.0.0.168])
	by mail2.wmptl.com (8.9.3/8.9.3) with ESMTP id KAA63493
	for <questions@freebsd.org>; Wed, 7 Jun 2000 10:00:43 -0400 (EDT)
	(envelope-from webmaster@wmptl.com)
Message-ID: <393E5325.6C99EC35@wmptl.com>
Date: Wed, 07 Jun 2000 09:50:29 -0400
From: Nathan Vidican <webmaster@wmptl.com>
Reply-To: webmaster@wmptl.com
X-Mailer: Mozilla 4.72 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: questions@freebsd.org
Subject: secondary MX host
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Is it possible to have a secondary MX host that will just queue incoming
messsages and relay them back to the main mailserver when it becomes
available? Here's the scenario:

Box 1:
 Hardware {
 	   AMD K62-500mhz
	   256megs RAM
	   two 15Gig ATA disks
	   }
 Purpose: primary mail server/radiusd
 Software: Livingston radiusd, compiled on machine; for machine
           Sendmail <not sure ver -am not at location right now)
	   cucipop 1.3
	   FreeBSD 4.0-STABLE-20000602

Box 2:
 Hardware {
 	   AMD K62-500mhz
	   128megs RAM
	   one 13Gig ATA disk
	   }
 Purpose: Secondary radiusd/mail server
 Software: Livingston radiusd, compiled on machine; for machine
           Sendmail <not sure ver -am not at location right now)
	   cucipop 1.3
	   FreeBSD 4.0-STABLE-20000602

Essentially, when box one becomes too overloaded, and/or is not active,
(eg during a reboot), I want box 2 to take over for it.
	The radius software pulls it's users/configuration from an NFS server,
both machines mount the same volume, and have read-only access to it;
write access to their logging directories (also mounted over nfs). The
machines themselves are connected on a small private subnet to the NFS
server, and directly to internet via ethernet, (tied to router/switch
obviously). Essentially, radius should not be a problem. The problem I'm
seeing is mail; if I mounted /var/mail over nfs to both machines users
would be able to access either to send or receive email no? (assuming
both machines have the same user/passwd of course -they do) Personally I
don't like this idea though; I'd rather the mailservers used their own
drives. I know there's got to be a way of doing this, just not sure how
to go about it.
	Any suggestions, comments, concerns, redirects or otherwise are more
than welcomed.

-- 
Nathan Vidican
webmaster@wmptl.com
Windsor Match Plate & Tool Ltd.
http://www.wmptl.com/


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