From owner-freebsd-current  Wed May 14 22:26:33 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id WAA00330
          for current-outgoing; Wed, 14 May 1997 22:26:33 -0700 (PDT)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA00324
          for <current@freebsd.org>; Wed, 14 May 1997 22:26:31 -0700 (PDT)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id XAA00025; Wed, 14 May 1997 23:26:26 -0600 (MDT)
Date: Wed, 14 May 1997 23:26:26 -0600 (MDT)
Message-Id: <199705150526.XAA00025@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Cc: David Nugent <davidn@labs.usn.blaze.net.au>, current@freebsd.org
Subject: Re: RELENG_2_2 
In-Reply-To: <17811.863652120@time.cdrom.com>
References: <199705141817.EAA01334@labs.usn.blaze.net.au>
	<17811.863652120@time.cdrom.com>
X-Mailer: VM 6.29 under 19.15 XEmacs Lucid
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.

Umm, so you are basically stating that *unless* you don't have a local
delivery agent, or you can guarantee that the delivery will never happen
when you're using dtmail it will work.

That's should like a pretty typical workstation setup (NOT!).



Nate