similar to: Corrupted index files

I'm running Solaris 9 Sparc with Dovecot alpha 5 and using maildir format.. I noticed in the log file the following error: dovecot: Dec 20 15:54:18 Error: imap(xxxxxxxx): open(/export/home/xxxxxxxx/mail/.Sent Messages/cur/1135013649.002916.mbox:2,Sab) failed: Too many open files I called the guy and asked him what he was doing... synching his folders. It hung for a while but finally

I'm installing dovecot and migrating from mbox to maildir. I've read several articles concerning this process but I can't seem to find the answer to one particular question. What is the default name of the inbox when using maildir format? I need to create this in advance for each user and I don't know what dovecot is expecting for the inbox directory name. -- Andy Cravens

I may have found a problem with the documentation concerning the subscriptions file. On the Dovecot web site there is a document that outlines the conversion from UW IMAP to Dovecot. The document says Dovecot's folder list is stored in ".subscriptions" However, I have found that Dovecot's folder list is really "subscriptions" without the preceding dot. Did

Has anybody successfully compiled alpha 3 with the newly released openssl-0.9.8? I just wasted the weekend trying to get dovecot to compile using the new openssl libs. Openssl-0.9.7d works like dream. Just wanted to know if anybody had this combo working.

I've been testing with alpha 3 and I am about ready to go production. I am switching from mbox to maildir and I'd like to know if there is a formula or rule of thumb for determining if your file system will have enough inodes to handle all the mail message files. I could write a script to look at each user's mbox files, count the number messages and calculate the average number

I just upgraded from alpha 3 to alpha 4 and now I'm getting these errors: dovecot: Nov 28 16:17:37 Info: Dovecot v1.0.alpha4 starting up dovecot: Nov 28 16:20:11 Info: imap-login: Login: user=<jdoe>, method=PLAIN, rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, TLS dovecot: Nov 28 16:20:13 Info: imap-login: Login: user=<jdoe>, method=PLAIN, rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx,

hello Timo, list, quick error-message question. A few of the accounts on my main mailserver are failing to log in with errors like this: dovecot: Mar 02 19:33:35 Error: imap(user at example.com): maildir_file_do(/var/lib/vpopmail/domains/example.com/user/Maildir) racing if I log in by telnet everything is fine, and from the source it looks like the error happens when dovecot fails to

Is there a way to move an imap subfolder up one level? I have a bad mouse and every now and then I have accidentally dragged an imap folder on top of another folder. I am unable to get the original folder back up one level. I've tried using several clients and I can't get it to work with dovecot. I keep getting a "folder already exists" message. I'm guessing dovecot

On 24.01.2017 11:31, Tom Sommer wrote: > On 2017-01-24 10:25, Aki Tuomi wrote: >> On 24.01.2017 11:13, Tom Sommer wrote: >>> On 2017-01-18 15:27, mkliewe at gmx.de wrote: >>> >>>> dovecot crashes when I switch the quota tracking from dict to count. >>> >>> I have the same problem, but I use 'dict:file' as quota backend - >>>

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

Hi, I'm experiencing a problem I need some pointers to debug. I'm running Dovecot 2.0.15 and have a client which keeps causing log-entries like: Nov 4 15:10:42 mail dovecot: imap (test at aaaone.net): Error: Corrupted transaction log file /mail/3340444/.TestMails/dovecot.index.log seq 2: indexid changed 1320419300 -> 1320419441 (sync_offset=0) Nov 4 15:10:42 mail dovecot:

Folks - I've been using Dovecot for some time now, but have only recently upgraded to 1.0alpha4. I'm struggling to get my configuration right and I'm seeing some truly bizarre issues. My Setup: Solaris 2.8 / Thunderbird / Procmail / Dovecot 1.0alpha4 My mail setup is only for me, so Dovecot runs at an odd port and under my userID. All my mail is in my home directory, which

Hi, I just upgraded from test80 to 1.0alpha1. I wanted to try something new on the lock_method, so I set: lock_method = fcntl, dotlock I got syslog complaints like: IMAP(username): Unknown lock_method: fcntl, dotlock Can one specify multiple file locking mechanisms? If so, what is the syntax (and can the syntax be shown in the comments of the .conf file)? Jeff Earickson Colby College

Please try if http://dovecot.org/nightly/dovecot-latest.tar.gz (or the CVS directly) works with you. I made a lot of changes to dovecot-auth, so I wouldn't want to make alpha4 release without some more testing in different environments. I'll release alpha4 in a few days, but it'll be basically same as this unless more bugs get fixed. Some of the changes include: - IMAP: We might

OS: CentOS 7 x86_64 Dovecot version: 2.2.31 (65cde28) (GhettoForge RPM) Filesystem: GlusterFS, but working on changing that. Only one server is receiving activity. Was getting messages about corrupt dovecot.map.index files. Changed to dotlock from fcntl to try to fix that. Reading symbols from /usr/libexec/dovecot/imap...(no debugging symbols found)...done. [New LWP 74012] Core was generated by

Hello - I know I am not the only one that will be trying, or has tried this before. Here are my questions! NFS Clients, multiple servers running dovecot - linux with 2.6 kernel with relevant patches (utime, etc) Backend - netapp filer End users - various clients all running IMAP It looks like 1.0.beta8 is definately the way to go. I have a few questions with regards to setup. Is it now

Hi, Our dovecot setup consists of two hosts running dovecot-1.0.beta9 with Maildir/indices stored on NFS(noac,actimeo=0 used). I am seeing these messages at times - but no real problems on the client side. Is this something to worry about? dovecot: Oct 17 10:33:31 Error: IMAP(user): Corrupted index cache file mailstore/user/Maildir/.mail.incoming/dovecot.index.cache: invalid record size

Hi all, I have some machines running FreeBSD and dovecot deployed. User's home dir is on NFS mount and I've found that dovecot only works with dotlock file locking mechanism, fcntl and flock failed. Now it causes problem with thunderbird (thunderbird is cachine connections) waiting forever and I noticed that dovecot is trying to acquire a lock but unsuccessful since the lock file is in

I have two servers pointing to an NFS mounted mail spool with dovecot.? Since I recently switched from using Dovecot v1.X, I have been experiencing high CPU use with the two Dovecot servers. I am not certain why they are not well behaved.? Here is the configuration information. This configuration is currently running at a load average of 17. /usr/sbin/dovecot -n # 2.1.15:

On 2016-10-31 22:04, Timo Sirainen wrote: >> Oct 31 10:52:37 imap(xxx at xxxx.xx): Warning: Locking transaction log >> file /mnt/nfs/xxx.xx/xxx/indexes/dovecot.list.index.log took 31 >> seconds (syncing) >> Oct 31 10:52:37 imap(xxx at xxx.xx): Warning: Locking transaction log >> file /mnt/nfs/xxx.xx/xxx/indexes/dovecot.list.index.log took 31 >> seconds