From owner-freebsd-security Sun Jun 9 15:07:17 1996 Return-Path: owner-security Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA27372 for security-outgoing; Sun, 9 Jun 1996 15:07:17 -0700 (PDT) Received: from hemi.com (hemi.com [204.132.158.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA27366 for ; Sun, 9 Jun 1996 15:07:13 -0700 (PDT) Received: (from mbarkah@localhost) by hemi.com (8.6.12/8.6.12) id QAA24430; Sun, 9 Jun 1996 16:06:55 -0600 From: Ade Barkah Message-Id: <199606092206.QAA24430@hemi.com> Subject: Re: FreeBSD's /var/mail permissions To: taob@io.org (Brian Tao) Date: Sun, 9 Jun 1996 16:06:55 -0600 (MDT) Cc: security@freebsd.org In-Reply-To: from "Brian Tao" at Jun 9, 96 11:56:10 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-security@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Brian Tao wrote: [Regarding QPOP not having permissions to create lock files] > An alternative would be to modify your newuser procedure to touch > and chown a .pop lock file for the user and configure your POP server > not to remove those files when the user exits. This is what I do currently; it feels like such a bad hack. > From the qpopper 2.2 install notes: > > h) KEEP_TEMP_DROP - Keep the .user.pop file around. It can be > used to determine when the last time a user has > accessed their mail. 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. =-) Off topic, I keep getting these syslog messages from QPOP: 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. Regards, -Ade ------------------------------------------------------------------- Inet: mbarkah@hemi.com - HEMISPHERE ONLINE - -------------------------------------------------------------------