similar to: dotlock file was deleted error

Hi Timo, Just tried squat in beta11. I also get the same error in the log: dovecot: Dec 10 14:21:17 Error: IMAP(joewong99:joew.outblaze.com): Corrupted squat uidlist file /mailfs/4/22/3/joewon g99:joew.outblaze.com at joew_outblaze_com/Maildir/dovecot.index.search.uids: Broken uidlists There is not change in my configuration file. # 1.1.beta11: /usr/local/etc/dovecot.conf log_path:

Hello, I have upgraded to Dovecot 1.0.0, I saw a lot of error in the dovecot.log file: Timeout while waiting for lock for transaction log file /fs/example.com/joewong/Maildir/dovecot.index.log where /fs is a NFS mounted directory. What can be the cause of this problem? How to prevent this from happening? Thanks! - Joe

Hi Timo, Is the dovecot index cache stored only standard header fields (from, to, cc, subject, content-type... )? What happen if there is non standard header, will it be cached? - Joe May the force be with you..

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

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

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

Hello Timo, I have installed 1.1 beta 8 with fts-squat enabled. I have added the plugin section in dovecot.conf. How can I actually make use of the full text index? Regards, - 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

Hello, >From time to time, I saw input / output error on rename() or pwrite_full(), for example: dovecot: May 02 05:46:18 Error: IMAP(joe): rename(/fs/joe/Maildir/.Sent Items/tmp/1178084777.P21895Q0M200058.tkodog.no-ip.com.com, /fs/joe/Maildir/.Sent Items/cur/1178084777.P21895Q0M200058.tkodog.no-ip.com:2,S) failed: Input/output error dovecot: May 02 06:29:49 Error: IMAP(victor): pwrite_full()

Hello, I have successfully configure dovecot to lookup my existing user database to lookup the homedir. However, I found the following from the log: dovecot: Apr 05 04:05:16 Info: IMAP(joewong99:tkodog.no-ip.com): Effective uid=1001, gid=1001, home=/mnt/mailmountpoint/4/22/3/joewong99:tkodog.no-ip.com at tkodog_no-ip_com dovecot: Apr 05 04:05:16 Info: IMAP(joewong99:tkodog.no-ip.com): maildir:

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

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

finally managed to locate the dump here the output: # gdb /usr/libexec/dovecot/auth /var/lib/systemd/coredump/core.auth.0.3a33f56105e043de802a7dfcee265a07.28130.1543516118000000 GNU gdb (GDB) 8.2 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it.

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

> 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

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

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

Hi, I've enabled autoexpunge for Trash and Junk. Now imap process core dumps occasionally. Tomppa > program terminated by signal SEGV (no mapping at the fault address) > 0xff0dc2e0: o_stream_get_buffer_used_size : ld [%o0 + 20], %o0 > Current function is notify_ok (optimized) > 13 if (o_stream_get_buffer_used_size(client->output) != 0) >

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.