search for: mail_nfs_index

...r.key userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } verbose_proctitle = yes protocol imap { imap_idle_notify_interval = 2 mins mail_max_userip_connections = 150 } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } ##EOF I use mailbox in nfs share. When i set the option "mail_nfs_index = yes" the dovecot fails to start. Looking at logs, only prompted this: "Feb 6 11:07:25 picapau kernel: [ 1436.376023] init: dovecot main process (4177) terminated with status 89" without more info.

Hey dovecot-users, did I miss anything anywhere about the configuration variables "nfs_storage" and "mail_nfs_index" being removed from the example configuration in 2.2? In 2.1 they where both in 10-mail.conf commented out and set to their default "no". But with 2.2 they are not in any of the exmaple config files anymore. doveadm is still showing the variables and they can be used as ever still....

Hi everybody, We use a Dovecot setup with GlusterFS. Dovecot 1.1.2 and GlusterFS 1.3.9. I enabled the following options (I don't have posix-locks translators): lock_method = dotlock dotlock_use_excl = no mmap_disable = yes mail_nfs_index = yes mail_nfs_storage = yes I receive the following error message. Aug 7 09:38:51 mta2 dovecot: POP3(somebody at domain.tld): nfs_flush_fcntl: fcntl(/var/vmail/domain.tld/somebody/Maildir/dovecot.index, F_RDLCK) failed: Function not implemented I think that I can disable mail_nfs_index to fix...

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

Hi, Does anyone have experience with bending the NFS recommendations to get better performance? The question is has anyone, with Maildir and the INDEX= on NFS (i.e. dovecot.index and dovecot.index.cache, set mail_nfs_index to no. If so, was it better to turn maildir_copy_preserve_filename to on or did it help to turn if off. The other question is did you play with turning off atime updates or changing the acmin* values? I know that the recommendation is do not do this. Fortunately Timo's screams won't re...

Hi, I need to place a maildir storage on a NFS filesystem, so I set up the config like this: mmap_disable = yes mail_nfs_storage = yes mail_nfs_index = yes mail_fsync = always lock_method = dotlock (also tried fcntl - local lockd is running, no success, now using dotlock, to be sure while debugging) The problem is that Dovecot (2.2.9/2.2.10 - the relevant code in mail-index.c is the same) logs a fatal error and quits the session (no daemon cras...

...x 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_disable = yes passdb { ? driver = pam } protocols = imap pop3 service anvil { ? client_limit = 203 ? process_limit = 1 } service auth { ? user = root } service imap-login { ? chroot = login ? client_lim...

...3 FreeBSD amd64 mailboxes (Maildir), control files and indexes are on NFS (v3,tcp) mail_nfs_storage = yes lock_method = fcntl [didn't touch the following] # Mail index files also exist in NFS. Setting this to yes requires # mmap_disable=yes and fsync_disable=no. mail_nfs_index = yes served by an Isilon s200 node (OneFS 6.5.5.22) procmail delivers in the same location through postfix-2.8.7 The filer shows *a lot* of such messages : 2013-08-02T14:12:29+02:00 <0.5> XXXX-10(id10) /boot/kernel.amd64/kernel: [lkf_delegate.c:2752](pid 46390="kt: dwt3")(ti...

...gt; 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_disable = yes >> passdb { >> ? driver = pam >> } >> protocols = imap pop3 >> service anvil { >> ? client_limit = 203 >> ? process_...

...suspect these errors to 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

The parameters listed for nfs installations (mmap_disable, doctlock_use_excl, mail_nfs_storage, mail_nfs_index) - are they necessary for data integrity, and/or do they compensate for NFS latency and improve performance? My understanding is the indexes are a critical part of a dbox storage, but on the other hand having local indexes is a major performance consideration. Is maildir a "better"...

...e.com> wrote: > You should review https://wiki2.dovecot.org/NFS to see that the settings > make sense. > > Aki > On 14.11.2018 12.00, Adrian M wrote: > > Thank you ! > I was little concerned that the following settings are not in line with > the new version: > > mail_nfs_index = yes > mail_nfs_storage = yes > mail_fsync = always > mailbox_list_index = yes > maildir_stat_dirs = yes > mmap_disable = yes > > > On Wed, Nov 14, 2018 at 10:19 AM Aki Tuomi <aki.tuomi at open-xchange.com> > wrote: > >> It should eventually wind down once...

...>, method=PLAIN, rip=::1, lip=::1, mpid=5540, secured, session=<7x47Jf76IQAAAAAAAAAAAAAAAAAAAAAB> Jun 4 10:09:20 mail03 dovecot: pop3(kiwi at oav.net): Fatal: nfs flush requires mail_fsync=always This is very strange since : # doveconf -n | grep -E 'sync|nfs' mail_fsync = always mail_nfs_index = yes mail_nfs_storage = yes So either there is some breakage somewhere or something that is buggy somewhere... Here is my doveconf -n : # 2.2.12: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 10.0-RELEASE-p3 amd64 auth_cache_size = 1 M auth_mechanisms = plain login digest-md5 cram-md5 au...

...ns: > rw,noatime,nodiratime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,nordirplus,proto=tcp,timeo=600,retrans=2,sec=sys,mountvers=3,mountport=1892,mountproto=tcp,local_lock=none > > On the Dovecot side we're running with: > lock_method = dotlock > mail_fsync = never > mail_nfs_index = no > mail_nfs_storage = no > maildir_very_dirty_syncs = yes > mmap_disable = yes > protocol lda { > ? mail_fsync = optimized > } > protocol lmtp { > ? mail_fsync = optimized > } > > Note: we're using Maildir and the usual "works for me(c), may not work &...

...Dovecot 2.0.13 on many servers, one for POP/IMAP access, others for LDA, others for authentification only, etc. All servers are accessing a shared file system, based on MooseFS (www.moosefs.org). The FS is mounted using FUSE. All my Dovecot servers have this configuration : mail_fsync = always mail_nfs_index = yes mail_nfs_storage = yes mmap_disable = yes (as adviced for NFS installation). But I'm still getting errors like this in POP/IMAP logs : Error: Corrupted index cache file /my_moosefs_fs/domain/user/indexes/.INBOX/dovecot.index.cache: invalid record size Sometimes my Dovecot LDA repairs...

Thank you ! I was little concerned that the following settings are not in line with the new version: mail_nfs_index = yes mail_nfs_storage = yes mail_fsync = always mailbox_list_index = yes maildir_stat_dirs = yes mmap_disable = yes On Wed, Nov 14, 2018 at 10:19 AM Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > It should eventually wind down once all the problems are fixed. Of course > if it d...

...to work at least on GFS2 on rhel 6.1. We have a two node cluster sharing two GFS2 filesystem - Index GFS2 filesystem to store users indexes - Mailbox data on a GFS2 filesystem The specific configs for NFS or cluster filesystem we used: mmap_disable = yes mail_fsync = always mail_nfs_storage = yes mail_nfs_index = yes fsync_disable=no lock_method = fcntl mail location : mail_location = mdbox:/var/vmail/%d/%3n/%n/mdbox:INDEX=/var/indexes/%d/%3n/%n But this seems not to work for GFS2 even doing user node persistence, maillog is plagged of errors and GFS2 hangs on stress testing with imaptest, many corrupt...

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 improvement. Can you please help. Regards Durga Prasad --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

...ot.org/ > - imap: SETMETADATA with literal value would delete the metadata value > instead of updating it. > - imap: When client issues FETCH PREVIEW (LAZY=FUZZY) command, the > caching decisions should be updated so that newly saved mails will have > the preview cached. > - With mail_nfs_index=yes and/or mail_nfs_storage=yes setuid/setgid > permission bits in some files may have become dropped with some NFS > servers. Changed NFS flushing to now use chmod() instead of chown(). I am seeing a lot of errors since the upgrade, on multiple client accounts: Info: Connection closed: re...

...METADATA with literal value would delete the metadata value > > instead of updating it. > > - imap: When client issues FETCH PREVIEW (LAZY=FUZZY) command, the > > caching decisions should be updated so that newly saved mails will have > > the preview cached. > > - With mail_nfs_index=yes and/or mail_nfs_storage=yes setuid/setgid > > permission bits in some files may have become dropped with some NFS > > servers. Changed NFS flushing to now use chmod() instead of chown(). > > I am seeing a lot of errors since the upgrade, on multiple client > accounts: &gt...