Date: Fri, 15 Feb 2002 14:56:01 -0500 From: "Robert Blayzor" <rblayzor@inoc.net> To: <jacks@sage-american.com>, <freebsd-questions@freebsd.org> Subject: RE: Sendmail POP Lock Message-ID: <029f01c1b65a$cc76e3a0$6f00000a@z0.inoc.net> In-Reply-To: <3.0.5.32.20020215120509.00e34990@mail.sage-american.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I'll post this back into the list as it was just a few days ago: If you are running Qpopper (POP3) this is a common problem. This happens when someone tries to pop into the same account when another session is already active. Or possibly the qpopper session crashed leaving the poplock file undeleted. There is no fix. You simply don't have multiple pop sessions. In practice, it's not a good idea to do so. -- Robert Blayzor, BOFH INOC, LLC rblayzor@inoc.net 'Life is like a spoonful of Drain-O, it feels good on the way down but leaves you feeling hollow inside' > -----Original Message----- > From: owner-freebsd-questions@FreeBSD.ORG > [mailto:owner-freebsd-questions@FreeBSD.ORG] On Behalf Of > jacks@sage-american.com > Sent: Friday, February 15, 2002 1:05 PM > To: freebsd-questions@freebsd.org > Subject: Sendmail POP Lock > > > I've just now set up a mail server using sendmail. Now, I see > that there is > a constant lock ".sageame.pop" on the main mail box "sageame". Popper > installed and sendmail is configured. What did I forget to do > to cause this > freezeup....? > > Best regards, > Jack L. Stone, > Server Admin > > =================================================== > Sage-American > http://www.sage-american.com > jacks@sage-american.com > > "My center is giving way, my right is in retreat; > ....situation excellent! ....I shall attack!" > =================================================== > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?029f01c1b65a$cc76e3a0$6f00000a>