On Sun, May 04, 2008 at 05:35:31PM +0300, Timo Sirainen wrote: > Do you still have this problem? You could try setting mail_location > explicitly to see if it changes anything > (http://wiki.dovecot.org/MailLocation). > > On Tue, 2008-03-11 at 17:25 -0400, Ben Julian wrote: > > Timo, > > The user can't access the mailbox directly under normal use > > circumstances. He doesn't have a smb share setup to allow him access > > to the mbox file. As far as I know, the only program besides dovecot > > doing editing of the mail is spamassassin, but that happens before the > > mail is written to the mbox. Perhaps I am misunderstanding your > > question? > > -Ben > > > > On Mon, Mar 10, 2008 at 9:26 PM, Timo Sirainen <[EMAIL PROTECTED]> wrote: > > > On Wed, 2008-03-05 at 15:17 -0500, Ben Julian wrote: > > > > Mar 3 10:37:00 servername dovecot: POP3(user): mbox sync: UID > > > > inserted in the middle of mailbox /var/mail/user (84873 > 84872, > > > > seq=2, idx_msgs=3) > > > > > > This is the main problem, these shouldn't happen. Can the user access > > > the mailboxes directly? > > > > > > See http://wiki.dovecot.org/MboxProblems > > >
This looks a lot like the issue I reported last month at <http://dovecot.org/pipermail/dovecot/2008-April/029991.html> which see for configuration details. At that time, I thought the problem was due to a conflict between Postfix adding a message to the mbox while dovecot was expunging messages. I have since seen the problem one more time apparently precipitated by two remote boxes accessing the same mailbox via separate dovecot processes simultaneously. I have since added pop3_lock_session = yes to the dovecot configuration, and I have seen no further problems, but it's only been 2 weeks since I made the above change so it's too soon to know for sure. -- Mark Sapiro mark at msapiro net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan