similar to: Quota count does not work with lock_method=dotlock

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 - > Maybe the error is due to quota_vsizes and not 'count'. > > // Tom Sommer Hi! What version of dovecot are you both using?

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 - >>>

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 - Maybe the error is due to quota_vsizes and not 'count'. // Tom Sommer

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 - >> Maybe the error is due to quota_vsizes and not 'count'.

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

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

Hi List, While testing with dovecot-1.0-test8 on our platform, I get al lot of these: May 11 11:42:50 mf1 dovecot: imap(user at domain.tld): Our dotlock file /var/mail/mounted/d/do/domain.tld/user/Maildir/.INBOX/ dovecot.index.log.lock was modified (1084268570 vs 1084268875), assuming it wasn't overridden This is probably due to some time-issues on our platform, and the load the

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

Hi there, I was wondering if someone can assist with clarifying why O_EXCL does not always work with NFS. Is it related to NFS protocol version support or export permissions mode out of the Celerra/Netapp ( e.g: mixed mode, unix file permissions ? ) Please advise. Thanks. Regards, new dovecot user.

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

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

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

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 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.

As of late our four node dovecot 1.2.13 cluster has been experiencing a massive number of these dotlock errors: Created dotlock file's timestamp is different than current time (1295480202 vs 1295479784): /mail/user/Maildir/dovecot-uidlist These dotlock errors correspond with very high load averages, and eventually we have to turn off all but one server to stop them from occurring. We first

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

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

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

Dear Samba experts, Initially we set up winbind to the following: idmap uid = 10000-20000 thinking that 10000 uids were sufficient for the number of users we would get. We also have defined our UNIX users from 20001 onwards. However, now I can see that our latest windows(idmap uid) users has uid 19123 and this troubles me. Since I cannot just "extend" the

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