Displaying 3 results from an estimated 3 matches for "uid_rec".
2005 Feb 08
2
Corrupted index file w/Procmail in FC2
...d from "new" folder to "cur"
folder, but I can't see my e-mail and Dovecot generates a "Corrupted
index file" in log file:
Feb 8 14:02:34 dlp1 pop3(epezoa): Corrupted index file
/users/operaciones/epezoa/maildir/.INBOX/.imap.index: index.next_uid
(14836) > uid_rec.uid (14825)
But, If I receive another e-mail (at "new" folder) and I try to get
messages, I get both.
My clients are Mozilla (with "pop3") and Squirrel (from another server
with "imaps"). Both have same behavior, so I think client is not
involved in this problem....
2005 Feb 09
3
Corrupted index file
I've recently switched from Courier-imap to dovecot and I'm impressed
with it's speed and reliability. However, my index file gets regularly
corrupted:
Feb 8 21:23:16 hive imap(hart): Corrupted index file
/home/hart/Maildir/.INBOX/.imap.index: index.next_uid (129) >
uid_rec.uid (128)
dovecot version: 0.99.13-3 Debian sid)
I use dovecot in combination with mutt, procmail and postfix.
If I rename the last received mail I can use my inbox folder again
(until the next time the index gets corrupted).
Debian bug# 294284
--
make install, not war
2004 Mar 12
1
blank line at the top of mbox
Hello,
It seems dovecop pop3 server sometimes inserts a blank line at the top
of the mbox. It only happens for certain users not all.
I'm not sure why it's doing that.
Looking back into the mailing list, I saw the same post in Oct 6, 2003
but there was no reply to it.
Is there a patch or fix that i can use to get around the blank line?
Thank you.
Ken