From owner-freebsd-isp Wed Dec 9 07:20:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA24027 for freebsd-isp-outgoing; Wed, 9 Dec 1998 07:20:42 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from magicnet.magicnet.net (magicnet.magicnet.net [204.96.116.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA24022 for ; Wed, 9 Dec 1998 07:20:40 -0800 (PST) (envelope-from bill@bilver.magicnet.net) Received: (from uucp@localhost) by magicnet.magicnet.net (8.8.6/8.8.8) with UUCP id JAA22258 for freebsd-isp@freebsd.org; Wed, 9 Dec 1998 09:56:05 -0500 (EST) Received: (from bill@localhost) by bilver.magicnet.net (8.9.1/8.9.1) id JAA13317 for freebsd-isp@freebsd.org; Wed, 9 Dec 1998 09:57:13 -0500 (EST) From: Bill Vermillion Message-Id: <199812091457.JAA13317@bilver.magicnet.net> Subject: Re: Leftover qpopper drop files In-Reply-To: from Mike Harshbarger at "Dec 8, 98 12:46:40 pm" To: freebsd-isp@FreeBSD.ORG Date: Wed, 9 Dec 1998 09:57:12 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Harshbarger recently said: > I've recently moved my mail server from a Solaris x86 platform > over to FreeBSD. I *love* the performance improvement, but I've > run into an irritating qpopper problem. As a friend put it: "Oh, > you've got the new qpopperdropper!" :) > I've ran qpopper 2.53 on both systems. Qpopper creates a temporary > drop file named /var/mail/.username.pop. On Solaris, this file was > deleted after use. They hang around in FreeBSD. If a new customer > happens to pick the same username as a old, deleted account, > they'll get this error when they try to pop their mail: ... > And then I get to jump in and either delete or chown the leftover > temporary drop file. Just be careful on chown. I've seen instances where a crash/disconnet of a users system leaves their current mbox in .whomever.pop. It can be used to recover, but you need to append the current mailbox contents to it if you are going to move it back. .... > It'd be easy for me to cron a script that would chown the > temporary files to the correct userid or simply delete ancient > ones, but I don't want to if I can fix this problem another way. So what constitues 'ancient'. I've seen popper dot files for casual users that are quite old. Chown has problems if the instance I mentioned above (though I've only seen it once) occures. I think the best place to handle this problem is in the script that removes the user, and have it remove the .user.pop file at the same time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message