search for: dotlock_try

...ILE) = -1 ENOENT (No such file or directory) 12:00:21.288614 open("/mnt/Mail/.indexes/.Sent/dovecot.index", O_RDWR|O_LARGEFILE) = 9 12:00:21.296814 alarm(60) = 0 12:00:21.297181 fcntl64(9, F_SETLKW64, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0} I have set the locks to dotlock_try followed by fcntl. The trace above seemed to fail with the dotlock, and proceed to fcntl? Here is the output from dovecot -n # 1.1.4: /etc/dovecot/dovecot.conf log_path: /var/log/dovecot.log log_timestamp: %Y-%m-%d %H:%M:%S login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/ima...

...l_cert_file = /etc/ssl/certs/imapd.pem ssl_key_file = /etc/ssl/certs/imapd.pem verbose_ssl = yes login_greeting = Dovecot ready. mail_location = maildir:~/Maildir mmap_disable = yes fsync_disable = no mail_nfs_index = yes lock_method = dotlock maildir_copy_with_hardlinks = yes mbox_read_locks = dotlock_try mbox_write_locks = dotlock_try mbox_dotlock_change_timeout = 120 protocol imap { } protocol pop3 { } protocol lda { postmaster_address = postmaster at example.com } auth_debug = yes auth default { mechanisms = plain passdb shadow { } userdb passwd { } user = root } dict { } plugin { }...

...p = "%Y-%m-%d %H:%M:%S " login_greeting = <COMPANY> ready mail_access_groups = mail otemail disk root mail_fsync = always mail_location = mbox:INDEX=/var/index/dovecot/%2.16Hn/%2.254Hn/%u mail_nfs_storage = yes mbox_lock_timeout = 2 mins mbox_min_index_size = 200 k mbox_read_locks = dotlock_try fcntl mbox_write_locks = dotlock_try fcntl passdb { args = /opt/dovecot/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocols = imap pop3 service auth-worker { user = dovenull } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl...

A mail user reported that he filled up his INBOX (despite reminders he was approaching his filesystem quota), and furthermore, he could not fix the situation because he couldn't expunge message he marked for deletion. The dovecot logs revealed the cause dovecot: imap(user): Error: open(/var/mail/user.lock) failed: Disc quota exceeded This created an impasse where a user cannot free

Hi All! Just noticed a strange behavior of the FS quota plugin on delivery stage. We use group FS quotas via NFS. And quota-tool says: --- Disk quotas for group #5751796 (gid 5751796): Filesystem blocks quota limit grace nfse:/export 1276 10240 10240 --- I run: --- cat ./test.eml | /usr/local/libexec/dovecot/deliver -e -n -d xxxx at xxxxx.xxxx --- and get: --- Quota

...doesn't exist either as a file or a directory in the named > directories. > > Is there a "filter" against dot-files being opened within the bowels of dovecot? You can disable dotclock altogether, but I don't think this is what you meant. You can use locking method "dotlock_try" rather than "dotlock" -- the former will ignore quota/permissions problems and plow on. (It still logs it.) You could also align luser's mail folder group with with luser's GID, which is usually what I do. Maybe locks are created even when files don't exist as there ma...

Im still finding a number of control directories that have the wrong permission: Jun 26 00:02:34 userimap13.xs4all.nl dovecot: IMAP(xxx): file_dotlock_create(/var/spool/mail/dovecot-control/g/gl/xxx/INBOX/.Apple Mail To Do/dovecot-uidlist) failed: Permission denied userimap1# ls -al "/var/spool/mail/dovecot-control/g/gl/xxx/INBOX/.Apple Mail To Do" total 8 drw------- 2 xxx user 4096

...aildir at this point. If I could get someone (or something) to the site and replace it with something much more suitable, I could have these people join the 21st Century. > You can disable dotclock altogether, but I don't think this is what you > meant. You can use locking method "dotlock_try" rather than "dotlock" > -- the former will ignore quota/permissions problems and plow on. > (It still logs it.) You could also align luser's mail folder group with > with luser's GID, which is usually what I do. What I meant was, are certain types of filenames &qu...

I am wondering if I really need to use dovecot quota functions or not. Assume for the moment, that, each system user has a quota defined using Linux quotas, and that the Maildir is within their quota limited directory. So, any mail (or files created by the user etc) that would exceed the quota obviously can't be created.? In such an environment, is there any advantage to implementing the same

...domain last_valid_gid = 19999 last_valid_uid = 19999 lda_mailbox_autocreate = yes log_timestamp = login_greeting = Ready. mail_location = mbox:/nfs/home/%n/mail:INBOX=/nfs/mail/%n:INDEX=/data/dc-cache/%n mail_nfs_storage = yes mail_temp_dir = /var/tmp mbox_very_dirty_syncs = yes mbox_write_locks = dotlock_try fcntl namespace { inbox = yes location = prefix = separator = / } namespace { hidden = yes list = no location = prefix = / separator = / } namespace { hidden = yes list = no location = prefix = ~/mail/ separator = / } namespace { hidden = yes list = n...

Hi, currently I have one new user with a problem. When she logs in to dovecot with pop3 from her apple mail, dovecot tells problems with the +w permission. Error: open(/var/mail/******) failed: Permission denied (euid=3462(******) egid=548(dozenten) missing +w perm: /var/mail) /var/mail is rw by root.mail I cant see why just this particular user has that problem/gets that messages. AFAIK no

...gs ## # Which locking methods to use for locking mbox. There are four available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # dotlock_try: Same as dotlock, but if it fails because of permissions or # because there isn't enough disk space, just skip it. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # lockf : May not exist...