similar to: Dotlock dovecot-uidlist errors / NFS / High Load

Stan, Thanks for the reply. In our case we have actually already done most of the work you suggested to no avail. We had rebuilt two new ntp servers that sync against two stratum 1 sources, and all our nfs clients, regardless of using dovecot, sync to those two machines. You bring up the difference between bare metal and hypervisor, and we are running these machines on vmware 4.0. All the

If I read the code correctly, only dotlocks are supported for locking of dovecot-uidlist. And I don't see any settings in the config file for it. As it turns out, dotlocks are very slow on my system, due to their implementation via hardlinks. Would it be possible to support other locking mechanisms for locking of the uidlist file? -jdb

I have a few clients that have more than one user in the same mailbox. I have my setup using fctrl for mailbox and index locking. My mail is stored on a network file system (gluster) and my indexes are stored on the local drive. I have a few issues: - My users mailboxes have issues where messages will be mixed up (you go to open a message and it gets a different message) - messages will

We are in the process of migrating away from Courier-IMAP/POP3 and Maildrop. I want to use Dovecot (LDA, IMAP, POP3). During my testing, it has worked great except for dotlocking on the dovecot-uidlist file. The problem: When a delivery is being made with deliver and a mail client has the mailbox open (Thunderbird in this case), neither Thunderbird or deliver can get a dotlock on the

Folks - Some time ago as I migrated to dovecot 1.0, I ran into all sorts of problems with file locks, and I tried various solutions. Apparently, in the process, I got a bit careless and removed all my dovecot-uidlist files. They're gone. My understanding, however, is that they should come back, but this doesn't happen. I've been forced to run with index=MEMORY in 1.0 for

Hi all, I've a dovecot server setup and occassionally clients cannot get mails from their inbox. When I inspect the maildir for that user, there is stale dovecot-uidlist.lock file, and imap process keeps waiting for release of the lock. Is there any other method to perform locking on dovecot-uidlist instead of using dotlock mechanism? It is creating maintenance problems if I need to remove

Hello, is dotlock supposed to work with NFS? I noticed that the default-locking method causes problems even with nfslockd started. Regards Marten

Hello, Running dovecot 1.1.6 on centOS 5 and RHEL 5. With the settings: pop3_lock_session = yes mail_privileged_group = mail mail_location = mbox:~/:INBOX=/var/spool/mail/%u mbox_read_locks = fcntl mbox_write_locks = dotlock fcntl and /var/spool/mail permissions: drwxrwx--x 2 root mail 4096 Nov 19 10:16 mail/ Trying to connect via POP3 results in this error: --- Nov 19 09:31:01

Hello, under what situation the error: dovecot-uidlist.lock was deleted (kept it 0 seconds ) will happen? I saw quite some of these in dovecot log. Thanks, - Joe

i finally manage to control access on public folder by File system permission. i have 3 test users. 1. tom 2. fmaster 3 . testmail tom and fmaster are a group called "news-own" and testmail user is a readonly one. here is my folder structure ill share dovecot -n output at the end of this email. drwxrwxr-t 2 tom news-own 4.0K Dec 4 19:08 tmp drwxrwxr-t 2 tom news-own 4.0K Dec

I've recently upgraded to 1.0.10 in hopes that this problem would go away but no luck. I've got some users at my company with large inboxes on maildir (say 22,000 messages). Their mailboxes are hosted on nfs and dovecot is configured to do dotlocking. Still I see messages like this continually in the logs (sometimes every hour or so): server dovecot: IMAP(user): dotlock

I have to make dotlock work because this openwebmail thing only supports one of dotlock or flock, but procmail delivery does dotlock and fcntl. procmail correctly creates a dotlock file in /var/spool/mail/username.lock when delivering, I can watch this with `while :; do ls -la | grep lock; done`. It works fine when lock_method=fcntl, but no dotlock file shows up in /var/spool/mail.

Hi, Is there a configuration element that would allow me to change the dot-lock name for the user's /var/mail inbox when it is locked? dovecot (correctly) acquires <username>.lock, but I'm having a problem with procmail where some obscure code path is preventing procmail's acquisition of a lock when it's that default name in /var/mail. The issue is not permissions

Anyone know how to setup dovecot with mdbox so that it can be used through shared storage from multiple hosts? I've setup a gluster volume and am sharing it between 2 test clients. I'm using postfix/dovecot LDA for delivery and I'm using postal to send mail between 40 users. In doing this, I'm seeing these errors in the logs Mar 21 09:36:29 test-gluster-client2 dovecot:

Hi there, I'm getting a lot of this message in production log: Created dotlock file's timestamp is different than current time (1232468644 vs 1232468524): /path/to/dovecot.index.log The IT guy swears the clocks are sincronized. Whe even have made a test in the machine running dovecot, inside the user's mailbox: # > foo; ls -l --time-style=full-iso foo; date -rw-r--r-- 1 root root

Hello. We are running dovecot 2.0.13 with mdbox+zlib on RHEL 5.7 x64, ext4. We use NTP. Indexes are in a iSCSI raid 10, mailboxes in raid5. No NFS. We have detected that sometimes all users get disconnected from roundcube at the same time. In dovecot logs we hundreds of lines like this: Nov 3 09:23:07 buzon dovecot: imap(mcrivero at mydomain): Warning: Created dotlock file's timestamp is

A shell script is deployed to synchronize time, the script is invoked hourly by crontab, and its content is as follows: #!/bin/bash service ntpd stop ntpdate 192.168.0.191 #it's a valid ntpd server in LAN service ntpd start chkconfig ntpd on Inspected the Linux log(Centos6.4 /var/log/messages), found the following fragment: Jan 7 14:00:01 host1 ntpd[32101]: ntpd exiting on signal 15 Jan 7

We have been communicating with the mailling list on another thread regarding dotlocking on the dovcot-uidlist over an NFS share, and I was hoping to get some ideas on whether or not a sql database would be a suitable location for storing the dovecot index files. Our though process so far has been that storing the index files on NFS with the maildir has not worked very effectively when we are

Hello, Autoexpunge is not working when used with dotlock locking. It seems to been broken since version 2.2.28. When autoexpunge is enabled and mailbox locking is set to dotlock all imap, pop and lmtp connections crash with the same error "file file-lock.c: line 287: unreached". Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 SASL-IR

Scenario: server PC abruptly switched off due to power cable problems (an UPS cannot solve this issue), so during shutdown Linux was not able to resinchronize the system clock. After a few hours the server come back on, Linux booted and the services (ntpd, dovecot and many others) started But the system clock was 45 minutes ahead, so: Jan 19 11:13:39 gw ntpd[2112]: synchronized to LOCAL(0),