From owner-freebsd-isp  Tue Feb 18 17:42:46 1997
Return-Path: <owner-isp>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA19965
          for isp-outgoing; Tue, 18 Feb 1997 17:42:46 -0800 (PST)
Received: from ns2.harborcom.net (root@ns2.harborcom.net [206.158.4.4])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA19954
          for <freebsd-isp@freebsd.org>; Tue, 18 Feb 1997 17:42:42 -0800 (PST)
Received: from swoosh.dunn.org (swoosh.dunn.org [206.158.7.243])
          by ns2.harborcom.net (8.8.5/8.8.4) with SMTP
	  id UAA27627; Tue, 18 Feb 1997 20:40:01 -0500 (EST)
Date: Tue, 18 Feb 1997 20:35:17 -0500 (EST)
From: Bradley Dunn <bradley@dunn.org>
To: spork <spork@super-g.com>
cc: freebsd-isp@freebsd.org
Subject: Re: closed NFS network
In-Reply-To: <Pine.BSF.3.95.970217134341.10802A-100000@super-g.inch.com>
Message-ID: <Pine.WNT.3.95.970218203005.-500155B-100000@swoosh.dunn.org>
X-X-Sender: bradley@harborcom.net
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 17 Feb 1997, spork wrote:

> I'm trying to patch together a small 100M ether network for NFS traffic
> between our POP server and shell server (and in the future, additional
> shell machines).  NFS looked like a good way to tackle this, as we can
> have the shell machine die, and PPP users can still do most everything but
> shell; our shell accounts are strictly a value-add.  Also, future shell
> machines could go on the same network and access the same mail spool that
> resides on the POP machine, and they could export /home out to the web
> server as well.

Look into IMAP. More info is at
http://www.imap.org/
In the documents section the is a paper called "Message Access Paradigms
and Protocols" that explains why IMAP is superior for mailbox access.


pbd