On Fri, Oct 19, 2012 at 10:52 AM, Randall Gellens <[email protected]> wrote: > Hi Keith, > > It sounds very much like what happens when two processes are trying to write > the file at the same time, which may result from a failure in the locking > protocol (e.g., the processes don't agree on the locking mechanism). > > - Are you running in server mode? > > - Do you have other processes that might access the spool (e.g., an IMAP > server, users accessing the spool directly, etc.)? > > - Do you have fast IO or locking options set? > > - Did you install your own local delivery agent? > > - If you are using server mode, you might try disabling it, more as a > diagnostic than a fix, to see if that stops the problem. >
Hi Randy, 1 - No, not running in server mode - Qpopper is invoked by xinetd. 2 - Nothing else should access the spool. Occasionally group users that share a mailbox log in to check mail but there is always a pop lock error at that time, so I assume the lock should prevent a problem? 3 - Fast I/O / Locking options - do you mean at a hardware level (e.g. RAID?) 4 - I have a procmailrc file that directs the delivery into the user's home directory as ".mail" Keith
