From owner-freebsd-isp Tue Apr 15 11:33:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA28063 for isp-outgoing; Tue, 15 Apr 1997 11:33:09 -0700 (PDT) Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA28054 for ; Tue, 15 Apr 1997 11:33:06 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970116) with ESMTP id OAA18986; Tue, 15 Apr 1997 14:32:03 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (WEBSPN/970116) with ESMTP id OAA03249; Tue, 15 Apr 1997 14:32:02 -0400 (EDT) To: Greg Stringfellow cc: isp@FreeBSD.ORG From: "Gary Palmer" Subject: Re: NFS/Mail Questions In-reply-to: Your message of "Tue, 15 Apr 1997 11:32:45 CDT." <199704151632.LAA03774@smokey.prismnet.com> Date: Tue, 15 Apr 1997 14:32:02 -0400 Message-ID: <3247.861129122@orion.webspan.net> Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Greg Stringfellow wrote in message ID <199704151632.LAA03774@smokey.prismnet.com>: > I'm looking into building a secondary POP/mail server and would like to use > NFS so that users on our shell account server can get mail. Looking at the > list archives, I've seen problems reported because of the lack of file > locking code in NFS. Don't. I just told them to use POP/IMAP compliant clients. If the don't like pine/mutt and insist on using elm, etc (which does NOT support POP or IMAP), there isn't much you can do. The only way I'd do it is if the client signed a disclaimer saying that any mail lossage is not your fault... Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info