Timo, Wow, thanks for checking back on this after all that time. I am actually still having problems, and just working around them by using a script to manually wipe out the inbox and index files for the user with the problem. I tried your suggestion of explicitly setting the mailbox location. It didn't seem to stop the problem, but it is hard to reproduce on demand. By sending the user a lot of forwarded mail, I was able to reproduce the issue once. I left it defined and tried Mark Sapiro's suggestion, adding " pop3_lock_session = yes", and so far, so good. I won't really know until a few days of use have passed. I'll be sure to let the list know how it turns out. Thanks for the follow up, guys, totally unexpected. -Ben
On Sun, May 4, 2008 at 10:35 AM, Timo Sirainen <[EMAIL PROTECTED]> 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 >> > >
