Re: [cobalt-users] [Qube2] Problem with Sendmail bug fix

[Glenn Parsons <gparsons@xxxxxxxxxxxxx>]

At 08:30 AM 3/5/2003 -0700, you wrote:
> In a previous message, Peter Low typed vigorously:
>
> >>Grant Hutchinson wrote:
> >>
> >>>Crap.
> >>>
> >>>I proceded to do this same patch on my Qube2. Everything worked fine and
> >>>looked as it should, but now I'm getting the following errors accessing
> >>>any of the accounts on the box:
> >>>
> >>>** Pop server error "-ERR [SYS/TEMP] maillock error 4:
> >>>
> >>>Any ideas on how to rid myself of these maillocks? Removing the lock
> >>>files doesn't help. They just get recreated the next time the accounts
> >>>get accessed. Even reverting to the previous version of sendmail doesn't
> >>>help. I still get lock files.
> >
> >My guess is its a qpopper problem.  Have you installed all the patches for
> >your machine?  Are you using pop-before-relay?
>
> The Qube is fully patched. I've run into the mail lock problem before,
> when the /var/cobalt/status file has become corrupted. Deleting that file
> and rebooting generally clears up any lock problems. Maybe I'll give that
> a go.
>
> How do I tell whether or not I'm using pop-before-relay?
>
> Grant
Hi Grant,

One way is to issue 'ps aux' on the server (this is one line from issuing a 
ps aux on a RaQ3):

root     22943  0.0  0.9  3644 2568 ?        S    Mar01   0:00 perl 
/usr/local/sbin/poprelayd -d

Also you can do this as root:

chkconfig --list poprelayd
poprelayd 0:off 1:off 2:off 3:on 4:off 5:off 6:off

The first line was the command I issued. The second was the response from 
the server.

Cheers,
Glenn Parsons

--
Glenn Parsons
Systems Administrator, Developer
mailto:dnsadmin@xxxxxxxxxxxxx OR mailto:gparsons@xxxxxxxxxxxxx
BGR Enterprises LLC/1Bigthink, 7361 Calhoun Pl., Suite 302, Rockville, MD 
20855
(301) 251-8570 x 207
http://www.1bigthink.com/