From owner-freebsd-current  Wed May 14 16:21:49 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id QAA12694
          for current-outgoing; Wed, 14 May 1997 16:21:49 -0700 (PDT)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA12682
          for <current@FreeBSD.ORG>; Wed, 14 May 1997 16:21:47 -0700 (PDT)
Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id QAA17815; Wed, 14 May 1997 16:22:00 -0700 (PDT)
To: David Nugent <davidn@labs.usn.blaze.net.au>
cc: current@FreeBSD.ORG
Subject: Re: RELENG_2_2 
In-reply-to: Your message of "Thu, 15 May 1997 04:17:12 +1000."
             <199705141817.EAA01334@labs.usn.blaze.net.au> 
Date: Wed, 14 May 1997 16:22:00 -0700
Message-ID: <17811.863652120@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> What happens when a user loses mail or has his/her mailbox
> trashed when there is a locking collision/race caused by
> dtmail and the local delivery agent using different locking
> methods?

We've been over this, and the feeling is that while this dysfunction
is bad, to someone who's on a disconnnected workstation and always
serializes access to the mailbox anyway (fetch mail via POP then read
it with dtmail), it's better than having dtmail simply refuse to
work at all.

> This is the real problem. Like many, I've been bitten by this
> when simply accessing a mailbox via nfs. It won't happen often,
> but it surely will.

Anyone who accesses a mailbox via NFS is living on the ragged
edge anyway. ;-)

					Jordan