One other question:  Will Cyrus go nuts if you kill all the deliver processes by
hand, instead of restarting the master process?
Just wondering.

-John

"Scot W. Hetzel" wrote:

> From: "John C. Amodeo" <[EMAIL PROTECTED]>
> > I got a weird problem here and I wanted to see if anyone else has
> > experienced similar problems.
> >
> > My current config is 2.0.16 / RH 7.1 / 2.4.3-12 kernel
> >
> > Once in a while, when a user goes to copy a message from their Inbox to
> > a subfolder, it locks their IMAP session,  After closing the mail client
> > (Webmail or Netscape Messenger), when they log back in, now they cannot
> > delete any messages in any of their folders, and, in addition, they
> > cannot write to any folders under their account.  Furthermore, Postfix
> > starts deferring mail because it cannot write to the users Inbox either.
> >
>
> >
> > It is almost as if Cyrus, or some other process, has a "lock" on the
> > account.  The only way to rectify the problem is to restart the master
> > process, which wouldn't be a problem if everyone else didn't get kicked
> > off of the system when you do.
> >
> > Has anyone experienced a similar problem?  Does anyone have any ideas?
> >
> Yes, we have experienced a similar problem w/1.6.24.  The problem that we
> experience is that deliver has locked the users Inbox, during an attempt to
> deliver a message.  Then when a user tries to delete/move a message, the
> server waits indefinitely, due to deliver has the mailbox locked.  The move
> operation does cause the message to be copied to the target folder, but the
> delete operation on the original folder doesn't complete.
>
> The only way we have been able to solve this problem was to kill all deliver
> processes.
>
> You might want to try and kill all lmtpd processes in 2.x, the next time
> this occurs.
>
> NOTE: 1. We run deliver in lmtp mode on 1.6.24
>       2. This problem occurs very infrequently for us (seen only 2 times in
> past year).
>
> Scot

Reply via email to