From owner-freebsd-security  Fri Jun  7 15:41:46 1996
Return-Path: owner-security
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id PAA00400
          for security-outgoing; Fri, 7 Jun 1996 15:41:46 -0700 (PDT)
Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA00395
          for <security@freebsd.org>; Fri, 7 Jun 1996 15:41:43 -0700 (PDT)
Received: from shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.5/8.7.3) with ESMTP id PAA00959; Fri, 7 Jun 1996 15:38:41 -0700 (PDT)
Message-Id: <199606072238.PAA00959@precipice.shockwave.com>
To: Nate Williams <nate@sri.MT.net>
cc: Barnacle Wes <softweyr@xmission.com>, security@freebsd.org
Subject: Re: FreeBSD's /var/mail permissions 
In-reply-to: Your message of "Fri, 07 Jun 1996 16:35:15 MDT."
             <199606072235.QAA01040@rocky.sri.MT.net> 
Date: Fri, 07 Jun 1996 15:38:40 -0700
From: Paul Traina <pst@shockwave.com>
Sender: owner-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Ah, good point.  I didn't think someone would actually yank the file
out from under mail.local.  Cough... hand me dunce cap for assuming
all the world was as stupid as elm.

Paul

  From: Nate Williams <nate@sri.MT.net>
  Subject: Re: FreeBSD's /var/mail permissions 
  > Their locking systems are irrelevant if they do not cooperate with
  > mail.local.
  
  See PHK's recent email.  Renaming the file to something else (in
  /var/mail) is a *real* effective way of making sure you lock the
  file. :)
  
  
  Nate