similar to: what does this mean: Warning: Error in custom flags file / Corrupted Indexes

Hi, I'm using version 0.99.10.8 on debian 2.4.26 and am getting this problem, can someone please shed some light over this? Aug 31 13:58:58 xxx imap(someone): file_wait_lock() failed with modify log file /var/mail/someone_new/Maildir/.INBOX/.imap.index.log: Resource temporarily unavailable and then: Aug 31 14:00:58 xxx imap(someone): Couldn't lock modify log file

Hi. Just got this error (1.1.rc4), is it something to worry about? Corrupted index cache file /.../Maildir/.Sent/dovecot.index.cache: used_file_size too large This is a shared mailbox with concurrent access. In general, can that usage pattern mess up the index? I am guessing "no", which is why I worry slightly about the warning. Cheers, Anders.

I see these errors more often than I'd like from Dovecot-1.1.2 on Mac OS X 10.5.4 (names and numbers elided): Corrupted index cache file %s: Corrupted virtual size for uid=%d: %d ! = %d Corrupted index cache file %s: Broken virtual size for mail UID %d Corrupted index cache file %s: used_file_size too large How bad are these? What should I look for to find out why they happen? Other

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! Suddenly since this afternoon the following happens: Sep 14 18:16:55 UnseenUniversity pop3-login: Login: gunter [127.0.0.1] Sep 14 18:16:55 UnseenUniversity pop3(gunter): Corrupted index data file / home/gunter/Mail/.imap/INBOX/.imap.index.data: Field 1 size points outside file (205408 / 205376) for record 4662 Sep 14 18:16:55 UnseenUniversity

Hi, I'm using Dovecot (dovecot-0.99.10p0) on OpenBSD-3.4 for few weeks now. When i connect to my IMAP account the connection is often closed by dovecot when i try to delete mails. I can see messages like this in log: Feb 29 18:47:00 po imap(mat at reynerie.org): Corrupted binary tree file /home/mat/Maildir//.INBOX/.imap.index.tree: used_file_size larger than real file size (1772 vs 1556)

I've been seeing lots of index cache file errors (using mbox on Solaris 8 sparc 64-bit, but with 32-bit Dovecot) since I switched my account to Dovecot 1.2.0 (we're still on 1.0.15 mostly, but I'm hoping to upgrade to 1.1.17+ this summer, or 1.2.x if it's stable enough). e.g. Error: Corrupted index cache file <path>/.imap/INBOX/dovecot.index.cache: field index too large (47

A bit quiet here, so here's some more thoughts about indexes. Even though I was thinking only how to make them usable with NFS (I wrote it to doc/nfs.txt), it then occured to me that exactly the same tricks would help with local filesystem indexes as well. Especially the lockless reading would help with lock contention issues I was worrying about earlier with shared mailboxes. Also it occured

Hello Timo, I'm having a problem with mbox that opening folder is slow when new mails are delivered to a folder. I'm delivering through the deliver program. Deliver updates index files but IHMO not completely correct. Therefore I compared index files before and after: 1.) Just delivered 2.) After accessing through imap via Thunderbird diff looks like (stripped down to the relevant

Hi, My apologies if this has been mentioned before, I haven't pulled up a google search yet. I run Dovecot from the package under OpenBSD 3.6 (dovecot-0.99.10.8). The problem I have is that occasionally dovecot corrupts an index file (I think), which causes the process to gradually creep up in usage, until it hits 99%, where it stays, without quitting. If I then fire up my mail client

# cat /proc/version Linux version 2.4.20-18.9 (bhcompile at daffy.perf.redhat.com) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Thu May 29 07:09:43 EDT 2003 # dovecot --version 0.99.10 I've just recently noticed a serious problem with my system. After about an hour or so I get errors in /var/log/maillog such as this; Sep 21 06:40:16 the-system imap(ray): opendir() failed with file

Hello, I'm in the process of migrating 0.99 dovecot maildir boxes to a pair of new machine. These servers were running the stable (etch) 1.0rc15 package of dovecot until yesterday and existing .customflags files were correctly converted to dovecot-keywords. Yesterday I upgraded to the (finally, thanks to who did this) 1.0.0 etch backports package and since then freshly migrated boxes get

Hello, i just switched from courier-imap to dovecot on a machine. The transition was painless except for one issue - when using the "Check mail" feature of kmail, one gets the message: "Unable to get information about folder customflags. The server replied: internal error..." So it looks like the server isn't properly hiding the .customflags file for some reason. I

Hi- Still getting a bunch of these: Apr 30 13:45:23 mercury mem[11056]: pop3(user1): Corrupted index file /users/78/user1/Maildir/.INBOX/.imap.index: used_file_size larger than real file size (4032 vs 1608) and the occasional: Apr 30 13:08:53 mercury mem[13507]: pop3(user2): Corrupted index file (in-memory index for /users/e0/user2/Maildir): Filename mismatch for UID 1:

OK. After checking the 0.99->1.0 migration documentation, it seems I've been a little confused between customflags and keywords. (Though this is partly due to my repeated requests for clarification being ignored.) The page (http://wiki.dovecot.org/moin.cgi/UpgradingDovecot) says 1.0 does not use .customflags any more. Now, I'm hoping they're still supported, in which case

Hi, I upgraded to test65 from 0.99 (mostly to get the namespace feature) and now it seems my .subscriptions and .customflags are showing up as mail folders in my IMAP client (Eudora). If I try and open those folders, of course I get an error. How can I configure dovecot so that these aren't displayed to my IMAP client? I looked through about 6 months of acrhives and couldn't find

Hi! I want to upgrade a Dovecot installation from 0.99.14 to 1.1.15, so I had a look at the following wiki article: http://wiki.dovecot.org/Upgrading?action=show&redirect=UpgradingDovecot The article http://wiki.dovecot.org/Upgrading/1.0 says something about .customflags -> dovecot-keywords and .subscriptions -> subscriptions change/conversion:

http://dovecot.org/test/ Pretty much the only change since test24 is a redesign of how cache file writing works. Reading works as before - without locks. Before (in 1.0-tests, 0.99 was worse) we used to just try to lock it. If it failed, we just didn't update cache. If it didn't fail, the lock could have been kept a long time. For example if a user was downloading a 10MB mail, the

http://dovecot.procontrol.fi/test/ Maildir syncing now works pretty much as described in my earlier mail. It was quite a large change, so please test this :) So the new and great features: - It's faster. - If someone renames maildir file just before we try to use it, we now resync the maildir and try to find it again. Before we just failed. It's also possible that the filename changed

Hi, I am upgrading a setup from Dovecot 0.99 to 1.1. There are a bunch of .imap.index* files that it appears that I can just delete, and they will be recreated as dovecot.index* files. Right? Next, there are some .customflags that I have now learned are not being converted to dovecot-keywords (as we skipped the 1.0 version, and the conversion code appears to be removed in 1.1). Is there some way

I'm wondering what I'd need to do to get the "important" flag set on an incoming message according to a pre-specified header. I know the problem of this not being a "joined-up" feature in standard email, but in practice many MUAs set headers like X-priority etc, and IMAP has an "important" flag that is the obvious mapping. I'm not really sure where