From owner-freebsd-current Wed May 14 22:16:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA29960 for current-outgoing; Wed, 14 May 1997 22:16:38 -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 WAA29955 for ; Wed, 14 May 1997 22:16:36 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id XAA29987; Wed, 14 May 1997 23:16:26 -0600 (MDT) Date: Wed, 14 May 1997 23:16:26 -0600 (MDT) Message-Id: <199705150516.XAA29987@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: Nate Williams , joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), current@freebsd.org Subject: Re: RELENG_2_2 In-Reply-To: <17931.863652798@time.cdrom.com> References: <199705142055.OAA28492@rocky.mt.sri.com> <17931.863652798@time.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Mail locking, as already been said *many* times. However, depending on > > usage, it may not bite anyone, or then again it might. It's kind of > > like serving your mail spool over NFS, most of the time it works, but > > sometimes it totally corrupts your mbox. > > But... This changes *nothing* with mail locking in existing tools > and, as you've stated several times, you don't really care about > dtmail so its own [dys]function is not apropos! You don't consider corrupting mbox as a bad bug? Either fix dtmail correctly, or not at all. Making it 'run' but corrupt email is worse than not running at all. "Gee, let's use FreeBSD/CDE, so we can lose email by design." Nate