I'm running Qpopper 4.0.3 on a Solaris 8 machine.  There are no local
users, just sendmail/procmail for delivery and qpopper for retreival.

The users are all automated processes which pull down the mail and
stick it into a database.  Since we installed this version, they've
started getting some errors.  This has shown up in their logs.

MailServerException: Unexpected response to command "QUIT" from POP server: -ERR 
maillock error 'Other lock error' (5) on '/var/mail/.dbuser.pop': No such file or 
directory (2)

So all the mail comes in, but the QUIT gives an error and the mail is
not deleted.  It all comes down the next time it's queried.  There are a
few hundred unique users on the box (all the same database), and they've
only seen the error a few times.  It's not reproduceable by anything
that I've tried.

We are running in server mode, since the process does delete all the
mail at the end.  Also, this process only grabs one mailbox at a time,
so I'm fairly sure there's nothing strange like multiple pop sessions
being attempted simultaneously.

Has anyone seen anything like this associated with 4.0.3?

Thanks!

-- 
Darren Dunham                                           [EMAIL PROTECTED]
Unix System Administrator                    Taos - The SysAdmin Company
Got some Dr Pepper?                           San Francisco, CA bay area
          < How are you gentlemen!! Take off every '.SIG'!! >

Reply via email to