similar to: timeout error in dovecot.log

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

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

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:

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

Hello - I know I am not the only one that will be trying, or has tried this before. Here are my questions! NFS Clients, multiple servers running dovecot - linux with 2.6 kernel with relevant patches (utime, etc) Backend - netapp filer End users - various clients all running IMAP It looks like 1.0.beta8 is definately the way to go. I have a few questions with regards to setup. Is it now

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

I have two servers pointing to an NFS mounted mail spool with dovecot.? Since I recently switched from using Dovecot v1.X, I have been experiencing high CPU use with the two Dovecot servers. I am not certain why 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:

I have, but I will be happy to review it once again. On 12/18/18 2:14 PM, admin wrote: > Am Dienstag, den 18.12.2018, 14:06 -0500 schrieb Albert E. Whale, CEH > CHS CISA CISSP: >> >> I have two servers pointing to an NFS mounted mail spool with >> dovecot.? Since I recently switched from using Dovecot v1.X, I have >> been experiencing high CPU use with the two

I have just upgraded to 1.1.8, hoping to fix these types of errors: Jan 20 10:39:27 laura deliver(xxxxxx at example.net): Broken file /srv/storage/mail/store/net/example/xx/xxxxxx/Maildir/dovecot-uidlist line 156: Invalid data: Jan 20 10:41:19 laura dovecot: POP3(yy.yy at example.at): Broken file /srv/storage/mail/store/at/example/yy.yy/Maildir/dovecot-uidlist line 2: Invalid data:

Hello list, we continue our tests using Dovecot on a RHEL 6.1 Cluster Backend with GFS2, also we are using dovecot as a Director for user node persistence, everything was ok until we started stress testing the solution with imaptest, we had many deadlocks, cluster filesystems corruptions and hangs, specially in index filesystem, we have configured the backend as if they were on a NFS like setup

Hi there, We have our mail boxes stored on a NFS server and we use maildir for mailbox storage. Some days ago we had a crush and SOME of the mailboxes get an error on QUERY: "EXPUNGE". eg: telnet localhost 143 Trying 127.0.0.1... Connected to localhost.localdomain. Escape character is '^]'. * OK Cabanova Mail ready. A01 LOGIN "hoeschen@***.com" "***" A01 OK

My recent migration from Courier-IMAP to Dovecot has been marred by these errors: Oct 24 12:12:40 server dovecot: IMAP(juha): Fixed index file ~user/Maildir/.Geekzone/dovecot.index: first_recent_uid_lowwater 431 -> 430 Oct 24 12:12:40 server dovecot: IMAP(juha): Corrupted index file ~user/Maildir/.Geekzone/dovecot.index: Duplicate header extension keywords Oct 24 12:12:40 server dovecot: child

Yes, multiple imap servers using one shared nfs storage. With the same config on 2.2.13 the public interface traffic was similar to the storage interface, around 100 mbps. After we switch to 2.2.27 the storage interface traffic jumped 10 times while the public interface stayed the same. This make us thinking that something is wrong and each time a user logs in the whole Inbox content is read

Hello all, We are facing extremely slow GFS2 issues in Redhat 7 64 bit. Backend is 16 Gbps FC SAN so no issues there. I have scoured the entire (anyways most of the) Internet and arrived at the following settings. mmap_disable = yes mail_fsync = always mail_nfs_storage = yes mail_nfs_index = yes mmap_disable = yes lock_method = fcntl Did a systemctl restart dovecot and did not find any major

I'm running beta7 on two machines, with maildir on NFS. I have lockd running on all machines. I've found that Dovecot is highly unstable with NFS when accessing a mailbox on more than one machine at the same time. Both dovecot machines have: mmap_disable = yes lock_method = fcntl NFS is version 3, exported from a third linux machine. All machines are running 2.6.9 kernel. Any ideas

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

Hi I have "problem" with dovect 2.2.13 from repo debian8 and I don't know how to solve it ... Server is a virtual (kvm) with debian 8.11 (postfix + dovecot from repo) and storage is mounting via nfs (I have use only one dovecot with external storage) All works fine but sometime ( after a few hours ) I have got a problem with dovecot cache (i use indexes) logs ->