search for: dotlocking

...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. mbox_write_locks are working correctly with mbox_write_locks = dotlock fcntl, the dotlock file shows up in the user's mail directory. However, dotlocking /var/spool/mail doesn't work: $ ls -la /var/spool/mail total 44 drwxrwxr-x 2 root mail 4096 Feb 25 17:39 . $ grep mail_privileged_group /etc/mail/dovecot.conf mail_privileged_group = mail Feb 25 17:45:45 anubis dovecot: POP3(despam_test_anubis): Effective uid=511, gid=100 Feb...

Hello, I'd like to make sure my understanding of the mbox locking strategy is correct : - "mbox_dotlock_change_timeout" directive : a process seeing that an already locked (by another process) mbox he want to access hasn't change for this amount of time, allows himself to override the lock ? If it's using fcntl, is it only possible to override ? -

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

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

...xxx>, method=PLAIN, rip=1.2.3.4, lip=5.6.7.8, secured --- The docs seem to indicate the above config / settings should work. Is this a bug? The reason we have dotlock as the primary format is due to procmail LDA from sendmail: --- procmail -v 2>&1|grep Locking Locking strategies: dotlocking, fcntl() --- I assume we have to make the "mbox_write_locks" match the procmail locking... Thanks. Rob

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

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

Hi How to solve this ? So many similar segfaults Thank you On 2018-11-30 06:11, Joan Moreau wrote: > ANother (very very long) example : > > # gdb /usr/libexec/dovecot/indexer-worker core.indexer-worker.0.3a33f56105e043de802a7dfcee265a07.21017.1543533424000000 > GNU gdb (GDB) 8.2 > Copyright (C) 2018 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or

Thanks for mySql For Squat vs Solr, Solr does not reach Squat by very far in terms of results : If I setup Solr, and search (via the search in Roundbube or Evolution) for a keyword or part of the keyword, the results are complete non sense. The diference between "search in full body" and "search in fields" does not even work. Solr with Dovecot seems very early beta

> On December 4, 2018 at 8:18 AM Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > We don't consider it as "very early beta". We consider it production ready. It is bit more work to set up though. FWIW, Squat has been deprecated since 2.0, so none of this should come as a surprise. https://wiki.dovecot.org/Plugins/FTS > Aki > > > On 04 December

...e code. There is no way having > setgid on the executable will work. The source drops the privledges long > before it tries to do a dotlock. > > This is an upstream problem. > > For now, I've disable dotlock, and use fcntl instead, as that is what exim > uses anyways. Is dotlocking still a work in progress or are we missing something here? -- Jaldhar H. Vyas <jaldhar at debian.org> La Salle Debain - http://www.braincells.com/debian/

We've just cut over to a new mail server running Dovecot 1.0.5. The underlying OS is RHEL 5. User mailboxes are stored in Unix mbox format on a local ext3 file system. The MTA on the system is the default RedHat version of Sendmail 8.13.8 with procmail for local delivery. We're using a combination of dotlock and fcntl style locking. The output of "dovecot -n" for this system

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 /home/user/Maildir/dovecot.index.log.lock was immediately recreated under us server dovecot: IMAP(user): file_dotlock_create() failed with file /home/user/Maildir/dovecot.inde...

I am using dovecot 1.0.rc15 (a similar problem occurred in rc10) on Solaris 9 (sparc). When working with a user who's home dir is on a local disk everything seems fine. But when that home is on an NFS-mounted disk things are very badly awry. Both the indices and the subscriptions file are being destroyed and what is left behind are files with names of the form .nfs72C034 etc. These files are

> On 04 December 2018 at 16:46 Joan Moreau via dovecot <dovecot at dovecot.org> wrote: > > > Hi > > How to solve this ? > > So many similar segfaults > > Thank you > > On 2018-11-30 06:11, Joan Moreau wrote: > > > ANother (very very long) example : > > > > # gdb /usr/libexec/dovecot/indexer-worker

We don't consider it as "very early beta". We consider it production ready. It is bit more work to set up though. Aki > On 04 December 2018 at 17:16 Joan Moreau <jom at grosjo.net> wrote: > > > Thanks for mySql > > For Squat vs Solr, Solr does not reach Squat by very far in terms of > results : If I setup Solr, and search (via the search in Roundbube

I'm running Dovecot 1.1 RC1. I believe I've done all the due diligence for making things working correctly over nfs. But I run into locking issues if I run over nfs. procmail is doing the delivery over nfs. uw-imap was ruining over nfs. dovecot is fine if its on the nfs server (i.e. it has local access to the disk, no nfs) I run into lock deadlocks if I run dovecot over nfs Users

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

Yes, but the bottom line is that Squat does the job needed for end users, Solr does not On 2018-12-04 16:53, Michael Slusarz wrote: >> On December 4, 2018 at 8:18 AM Aki Tuomi <aki.tuomi at open-xchange.com> wrote: >> >> We don't consider it as "very early beta". We consider it production ready. It is bit more work to set up though. > > FWIW, Squat

Hello, Dovecot documentation states that the "random redirects to multiple servers" NFS solution is to be avoided and I'm investigation the actual risks of it and a way to put it to test. I'm running dovecot-1.2.6 with Maildir (indexes, mailboxes and control files are all on NFS) and I'm using procmail instead of deliver as the LDA. 1. Documentation says : "Dovecot