From owner-freebsd-questions Wed Apr 1 00:14:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09610 for freebsd-questions-outgoing; Wed, 1 Apr 1998 00:14:29 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from dove.peace.com.my (peace.com.my [202.184.153.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09596 for ; Wed, 1 Apr 1998 00:14:26 -0800 (PST) (envelope-from panda@peace.com.my) Received: from lovebox (love.com.my [202.184.153.17]) by dove.peace.com.my (8.8.5/8.8.5) with SMTP id PAA17887; Wed, 1 Apr 1998 15:56:49 +0800 (SGT) Date: Wed, 1 Apr 1998 15:56:49 +0800 (SGT) Message-Id: <3.0.32.19980401161908.009ef270@peace.com.my> X-Sender: panda@peace.com.my X-Mailer: Windows Eudora Pro Version 3.0 (32) To: Dean Hollister , Doug White From: chas Subject: Re: Mailbox locked Cc: FreeBSD Questions Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:43 AM 4/1/98 +0800, Dean Hollister wrote: >>>Hello, >>> >>>We have a user who's mailbox has been locked somehow. I need to clear the >>>lock but cannot locate a lock file anywhere. Where would I expect to find >>>it? >> A POP locked mailbox? Check for a file /var/mail/${USERNAME}.pop.lock (or >> .${USERNAME}.pop.lock). >> >> The campus Solaris POP server has this problem constantly. They finally >> created a script called 'unpop' that kills this file. > >Hmmmm.... Nothing like this is present... > >Elm, and Pine both report mailbox is read-only... Not sure I can help you since you mention Elm/Pine but I've suffered similar locked mailboxes when the user's mail client chokes and crashes whilst downloading/decoding a very large attachment or many messages. I attribute the subsequent "mailbox locked" errors to the socket connection not being closed in an orderly manner. In such circumstances, I've checked for lock files but found none. Usual cure is to restart the POP server and inetd but that rarely works... so I resort to the usual cure-all : reboot. (obviously it would be nice to not have to do this and disrupt all the other users so I'm all ears for surefire ways of curing this : one user in particular managed to lock his mail box very frequently) chas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message