search for: lock_method

...uot;quota count" + "quota clone" combination. I'm loading the "quota_clone" plugin, and: #quota = dict:User quota::proxy::quota quota = count:User quota quota_vsizes = yes quota_clone_dict = proxy::quota It works on a maschine where I'm using NFS with lock_method=fcntl. It's crashing on another maschine where I'm using NFS with lock_method=dotlock. See below. Sadly I have to use dotlock, because of the NFS server. It looks like quota count does not (yet) work with dotlock? Michael Jan 17 18:46:04 XXXX dovecot: imap-login: Login: user=<XXXX...

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

...ich mounts my home directory. Typical entry from .procmailrc: :0 * ^(From|To|CC):.*@.*\<si2.org Maildir/.SI2/ Highlights from dovecot.conf: #default_mail_env = maildir:%h/.mail/Maildir:INDEX=/var/tmp/mario/dovecot default_mail_env = maildir:%h/.mail/Maildir:INDEX=MEMORY mmap_disable = yes #lock_method = flock lock_method = fcntl #lock_method = dotlock protocol imap { listen = *:2143 } auth_worker_max_count = 0 auth default { mechanisms = plain userdb passwd { } } When I run as above (INDEX=MEMORY), I have access to all my mail, but I'm seeing literally thousands of .nfs file...

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

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

...fp_offset = 48, overflow_arg_area = 0x7ffd7009f5d0, reg_save_area = 0x7ffd7009f510}} #5 0x00007fa2630a344f in file_lock_do (fd=fd at entry=20, path=path at entry=0xbb5868 "/gnoc/mail/home/bgeels/mail/mailboxes/Junk/dbox-Mails/.vsize.lock23f657caa43d8796", lock_type=lock_type at entry=1, lock_method=lock_method at entry=FILE_LOCK_METHOD_DOTLOCK, timeout_secs=0, error_r=error_r at entry=0x7ffd7009f768) at file-lock.c:285 lock_type_str = 0x7fa2630e6948 "write-lock" started = 1502905468 ret = <optimized out> __FUNCTION__ = "file_lock_do" #...

Hi all, I've a little pb with 1.0-stable on nfs share without lockd : with : - lock_method = dotlock - mmap_disable = yes I've : - dovecot: Jul 22 11:58:33 Error: IMAP(xxxxxxxx): open() failed with index file (null): Bad address with : - lock_method = dotlock - mmap_disable = no I've : - dovecot: Jul 22 11:59:47 Error: IMAP(xxxxxxxx): lock_method=dotlock and mmap_disa...

...king transaction log >> file /mnt/nfs/xxx.xx/xxx/indexes/dovecot.list.index.log took 31 >> seconds (syncing) > > This just means something is being slow. Not necessarily a problem. > Although it could also indicate a deadlock. Is this Maildir? Did you > say you were using lock_method=dotlock? I removed dotlock some time ago (using director) and switched to: lock_method = fcntl mail_fsync = always With "count" as quota backend I get a lot of these errors on the director: imap-login: Error: proxy(xxx at xxxx.xxx): Login for xxx.xxx.xxx.xxx:143 timed out in state=2...

...hy 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: /etc/dovecot/dovecot.conf # OS: Linux 3.10.54-server-2.mga3 i686 Mageia 3 base_dir = /var/run/dovecot/ disable_plaintext_auth = no lock_method = dotlock login_greeting = SpamZapper Email ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c mail_debug = yes mail_fsync = always mail_location = maildir:~/Maildir mail_nfs_index = yes mail_nfs_storage = yes mail_privileged_group = mail mbox_lock_timeout = 15 mins mmap_...

...ons are round-robined between imap servers? I've seen various people using different actimeo settings, some set at 0, some slightly higher - as much as 30. Can anyone speak on experience they have had with netapps on this subject? The following sound like they are required: mmap_disable=yes lock_method=dotlock Has anyone been successful with fnctl() on netapps with dovecot? Thanks in advance! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://dovecot.org/pipermail/dovecot/attachments/20060613/eff9d8b8/attachment.html

i'm working with exim 4.60, with mbox, and dovecot dovecot-1.0.beta7, and filesystem quotas default_mail_env = mbox:~/mail::INBOX=%h/mbox:INDEX=/tmp/%u lock_method = dotlock fcntl mbox_read_locks = dotlock fcntl mbox_write_locks = dotlock fcntl The home of users is /home/usuaris/user Where place dovecot the lock file?

Hello, I'm deploing a new email cluster using Dovecot over GFS2. Actually I'm using courier over GFS. Actually I'm testing Dovecot with these parameters: mmap_disable = yes mail_fsync = always mail_nfs_storage = yes mail_nfs_index = yes lock_method = fcntl Are they correct? RedHat GFS support mmap, so is it better to enable it or leave it disabled? The documentation suggest the use of flock. What about it? Thanks, Andrea -- ---------------------------------------------------------------- Don't talk with a full mouth ... or with an...

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

...>> This configuration is currently running at a load average of 17. >> >> /usr/sbin/dovecot -n >> # 2.1.15: /etc/dovecot/dovecot.conf >> # OS: Linux 3.10.54-server-2.mga3 i686 Mageia 3 >> base_dir = /var/run/dovecot/ >> disable_plaintext_auth = no >> lock_method = dotlock >> login_greeting = SpamZapper Email ready. >> login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c >> mail_debug = yes >> mail_fsync = always >> mail_location = maildir:~/Maildir >> mail_nfs_index = yes >> mail_nfs_storage = yes...

...be responsible for customers complaining about downloading mails twice, I'd like to fix them. Our setup has multiple servers sharing the same NFS-mounted directory for maildirs and indexes; we have set mmap_disable = yes dotlock_use_excl = yes fsync_disable = no mail_nfs_index = yes lock_method = fcntl As far as I can tell, for at least one of these errors, there was no concurrent access to the mailbox in question. What can I do to solve this problem, or to analyze it further? Ulrich

...ate_locked(/.../Maildir/.vsize.lock) failed: Is a directory The directory in question # ls /.../Maildir/.vsize.lock/ cur/ dovecot.index.log dovecot-uidlist maildirfolder new/ tmp/ so Dovecot seems to think this to be an IMAP folder. I am using Dovecot 2.2.27 under Debian, built from source, the lock_method is set to fnctl, and the quota plugin uses the maildir method. Can somebody advice me on how to fix this? Best regards, Thorsten -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20180124/66ebcdb2/attachment.html...

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

...cutable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login verbose_proctitle: yes mail_extra_groups: mail mail_location: maildir:~/Maildir dotlock_use_excl: no fsync_disable: yes lock_method: dotlock maildir_copy_with_hardlinks: no mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins(default): fts fts_squat mail_plugins(imap): fts fts_squat mail_plugins(pop3):...