From owner-freebsd-security Sun Jun 9 16:38:06 1996 Return-Path: owner-security Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA12294 for security-outgoing; Sun, 9 Jun 1996 16:38:06 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA12278 for ; Sun, 9 Jun 1996 16:38:03 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id TAA15820; Sun, 9 Jun 1996 19:37:00 -0400 (EDT) Date: Sun, 9 Jun 1996 19:37:05 -0400 (EDT) From: Brian Tao To: Ade Barkah cc: security@freebsd.org Subject: Re: FreeBSD's /var/mail permissions In-Reply-To: <199606092206.QAA24430@hemi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-security@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 9 Jun 1996, Ade Barkah wrote: > > Actually, this is not needed. The same set of permissions which > prevents QPOP from creating the .user.pop file also prevents it > from removing the lock file. =-) It complains about not being able to remove the file though, doesn't it? I don't know, since I haven't experimented with it (I use a mode 1777 /var/mail/.tmp). > popper[20737]: @remote-host: -ERR POP EOF received > > Any ideas why this might be happening ? I'm sure I'm not the only > one seeing many of these. It seems like a chronic problem on the > client side. Hrmmmm... I remember some sort of problem like that with an older 2.1.x qpopper that forced me to go back to the cac.washington.edu POP daemon. I'm a Pine user myself, so POP-related problems don't usually surface unless I can force myself to use Netscape to read mail (ick!) and look for anomalies. -- Brian Tao (BT300, taob@io.org, taob@ican.net) Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't"