similar to: Corrupted index & index data file

I am having a problem with Dovecot and imap; users are not being able to empty their trash from time to time. Here is what I am running: [root at xxxx root]# rpm -q dovecot dovecot-0.99.13-3.FC3 [root at xxxx root]# uname -a Linux xxxx 2.6.12-1.1381_FC3smp #1 SMP Fri Oct 21 04:03:26 EDT 2005 i686 i686 i386 GNU/Linux [root at xxxx root]# Several times a week different users get the following pop

We are using dovecot-0.99.13-3.FC3; the users use IMAP. I have had several of these today where the user cannot write to their Sent folder on the server. The users do own everything in their home dir: [root at jidmail lcrdjav]# file Sent Sent: ISO-8859 HTML document text What is up with the HTML, I am not used to seeing this in any of the IMAP folders ? -- James H. Edwards Network Systems

I am seeing lots of these in my logs and there are often a hundered or so imap/dovecat process running. I am running RC Core3. Can anyone shead some light on how to correct this ? Jun 16 08:38:24 jidmail dovecot(pam_unix)[27653]: check pass; user unknown Jun 16 08:38:24 jidmail dovecot(pam_unix)[27653]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= Jun 16 08:38:24 jidmail

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:

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

I'm using alpha 5 and I'm getting "Corrupted index cache files" errors on one user's account. I found several posts in the mail archives on this subject and concluded from the responses that it's not a serious problem because Dovecot can deal with it. I deleted the index files and they were recreated but the error persists. The end user did not notice any problem

Hello, we're experiencing an odd issue after combining two vDisks used for mail storage into one big new LVM. We've done this in the past successfully and didn't experience a lot of problems. We stopped all services (dovecot/postfix) to ensure that mailbox contents (Maildir) will not be changed, rsynch'ed the mail to the new disks and restarted everything. When we restarted

I've searched the archives and find a lot of references to corrupted indexes but can't seem to find any solutions. It seems like folks either have the problem or they don't. We recently migrated from a RedHat Linux server to an OpenBSD 3.7 server (both using dovecot). Imap was working flawlessly on the RedHat box but now gives numerous index errors. I then upgraded to

Hi - I've got two copies of Dovecot installed on my server (don't worry, talking to two different sockets for authentication, with two different sets of filenames using options in configure), and I found at least one instance where the index file for my INBOX (on my own account, in fact) got corrupted. So badly so that when I connected via IMAP and selected my INBOX, it said there were no

Hello, Ferret created a 4.5GB> index file. $ 4534029210 2007-02-26 12:46 _el.cfs The creation of the index went smoothly. Searching through this index also works fine. However whenever I try to get the contents of an indexed document I get an error when the document number is above 621108: irb(main):080:0> searcher[621108].load IOError: IO Error occured at <except.c>:79 in xraise

This one has me stumped. After upgrading from dovecot-1.0-beta8 to dovecot-1.0-rc6, I can't start dovecot from /etc/rc.d/init.d/dovecot. I can start dovecot directly from the command line (/usr/sbin/dovecot). I can still use /etc/rc.d/init.d/dovecot to query the status of dovecot and shutdown dovecot, but I can't use it to start dovecot. It just says "FAILED". diff scan of

On Fri, Jul 21, 2017 at 08:50:16PM +0200, Robert Schetterer wrote: > you should avoid this > one solution is to use loadbalancers with persistance We had been using a loadbalancer with persistence to reduce the problems, and today I switched to everything running on a single box to avoid any cross-node contention. Unfortunately, the problem still happens, even when they were all running

Hello everyone. I am new to the list, so forgive me if this has been discussed already. My configuration is as follows: Fedora Core 3, fully patched through yum through today. Dovecot 0.9.9.13 Postfix 2.1.5 Using Maildir with Mail stored in ~/Maildir My issue is that, for some odd reason the inbox file index gets corrupt, There is no rhyme or reason as to why it happens or when, but a

Hi, On saturday one of our dovecot machines had an OOPS, and we had to powercycle it. When it came up, it did a filesystem fsck (ext4) and fixed a couple things, but nothing in lost+found. Now, about 50 users have a problem where their indexes are corrupted. Dovecot tries to fix them, but for some reason it is failing. The users are seeing their mails duplicated and they cannot delete mails. I

Hi, I have recently migrated (under emergency conditions) a dovecot imap/pop based server to a new instance. The mailboxes used mdbox format and due to various screwups I had corrupt indexes. I thought I'd cleaned this up but then I found that this new instance hadn't been set up correctly for nfs. Long story short, I still get users with new cases of corrupt indexes. The symptom is imap

A new employee started today, when logging into his new mailbox this morning during a walk-through I got a nasty server error response in Thunderbird - something I never see, DC runs smooth as butter for us. Checking the server log I see this: == snip == dovecot: Jul 09 09:38:54 Error: IMAP(xxxxxxx): Maildir /home/x/xxxxxxx/Maildir sync: UIDVALIDITY changed (1183406107 -> 1183999134)

On Fri, Jul 21, 2017 at 03:25:39PM -0600, Bruce Guenter wrote: > We had been using a loadbalancer with persistence to reduce the > problems, and today I switched to everything running on a single box to > avoid any cross-node contention. Unfortunately, the problem still > happens, even when they were all running imap on a single box. I just confirmed this. One of the mailboxes was

Greetings! During migrating i686 installation of ArchLinux to x86_64, all filesystem was rsynced to a new location. Maybe this somehow relates to the problem that has appeared after migrating and that did not happen before: during backuping the system, rsync reports the following error message: rsync: set_acl: sys_acl_delete_def_file(var/log/journal/remote): Operation not supported (95) The

Hi all, I got a problem with a Dovecot IMAP/POP installation. Since a recent failure of our distributed file system (no loss of data btw), Dovecot seems to have a problem with index cache files. For a lot of accounts, I have this error in logs: Error: Corrupted index cache file /xxx/yyy/zzz/indexes/.INBOX/dovecot.index.cache: invalid record size If I delete all files from /indexes/

Hello, I'm running Dovecot 1.1.13 on FreeBSD 7.0-RELEASE and I'm receiving a large number of errors much like the following: dovecot: Jun 08 09:27:04 Error: IMAP(x at x.x): Corrupted index cache file /nfs/x.x/x/Maildir/dovecot.index.cache: Corrupted physical size for uid=2284: 5312 != 5217 dovecot: Jun 08 09:27:04 Error: IMAP(x at x.x): Corrupted index cache file