Technical article 110212

Some clients attempting to pop mail from the server are unsuccessful.

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4

Written · Last revised

Problem

Some clients are not able to pop their mail successfully.  Common
errors include:
Could not login to mail server.

Mailbox is being read by another session.

You are already reading this folder from another mail session.

Or, the POP request may fail with another error.

Cause

There could be a lock file left by a popper or mail process that
was unexpectedly terminated.  The lock file contains the process
ID of the popper process that was accessing the mailbox.
The filename is made up of the inode number of the specific
user's mailbox, followed by ".298".  For example, if the command
"ls -i /usr/spool/mail/tom" reports 47352, you would expect the
mail lock file for the account "tom" to be "/tmp/47352.298".
This lock file gets created by popper when the user attempts to
retrieve mail and also when mailx is used to read mail.  The lock
file is owned by the user account, with 400 permissions.

Solution

If the mail is not being read by another process, remove the lock file and try to POP the mail again.

SCO OpenServer 5.0.5 also has an updated locking mechanism, so upgrading to that release (or later) may help.

See also

ta107717, "Clients popping mail from the server are causing files to be left in /tmp on OSR5."

NOTE:     This Technical Article was kindly submitted by:
Authorized Support Center, ESS
email: support@esshelp.com

From the Xinuos technical article database, record 110212. Reproduced with permission. The original is at www.sco.com/ta/110212, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.