Timo and Mark,
It appears that my problem was due to our configuration of the
user's several home directories - we had different usernames created
for this individual, but two of the home directory definitions in
/etc/passwd were unintentionally pointing to the same place, causing
the dovecot
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.
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
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
Asheesh,
Sorry about the long delay. I tried upgrading to version 1.0.12,
which I understood to be the newest release for CentOS 5.I am
still experiencing the problem. What should I try next?
Thanks,
Ben
On Wed, Mar 5, 2008 at 5:51 PM, Ben Julian [EMAIL PROTECTED] wrote:
Just read
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?
Hello Dovecot List,
I am a bit of a sysadmin novice and this is my first time emailing,
so please let me know if I have left some critical information out. I
am supporting a small office network supported primarily by linux
servers. All of my users are using dovecot as a pop3 daemon on a
On Wed, 5 Mar 2008, Ben Julian wrote:
All changes resulted in only a brief (1-2hr) cessation of the problem.
I've subscribed for a month or so now and searched the archives, but
if I missed a solution to this in there, I apologize.
That sounds like a drag. Let's see if we can help you.
Can
