From owner-freebsd-questions Fri Feb 15 12:12: 8 2002 Delivered-To: freebsd-questions@freebsd.org Received: from marlo.eagle.ca (marlo.eagle.ca [209.167.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 52ECC37B400 for ; Fri, 15 Feb 2002 12:12:05 -0800 (PST) Received: from Bob (staff.eagle.ca [209.167.16.15]) by marlo.eagle.ca (8.11.3/8.11.3) with ESMTP id g1FK94c85828; Fri, 15 Feb 2002 15:09:14 -0500 (EST) (envelope-from freymann@scaryg.shacknet.nu) From: freymann@scaryg.shacknet.nu To: jacks@sage-american.com, freebsd-questions@freebsd.org Date: Fri, 15 Feb 2002 15:12:59 -0500 MIME-Version: 1.0 Subject: Re: Sendmail POP Lock Message-ID: <3C6D257B.101.6D493E@localhost> In-reply-to: <3.0.5.32.20020215140016.00e34990@mail.sage-american.com> References: <3C6D19E9.28323.4016AE@localhost> X-mailer: Pegasus Mail for Windows (v4.01) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 15 Feb 2002 at 14:00, jacks@sage-american.com wrote: > The strange things is that: > 1) the log did not show anything happening, but the mailbox and the > ".mailbox.pop" where locked in tight showing a constant connection > (per the time stamp). There was zero bytes in both files. Just because there's a 0 byte .mailbox.pop file left behind, that DOES NOT mean the mailbox is locked. There's a separate mailbox.lock file that does that dude. If you see a 0 byte .mailbox.pop file, it's nothing to worry about. If the mail account was really locked you'd be seeing "pop lock busy" errors in your /var/log/messages file. You may be chasing a ghost here (in other words, this is normal). > 2) grep did not show popper as active This is good. gf To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message