search for: mail_nfs_

Hi @ll, has anybody tried this with dovecot yet ? http://www.xtreemfs.org/ -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

...on our servers. Why is dovecot trying to use fcntl() ? I explicitly set it to use dotlocks in the dovecot config: # 1.1.6: /etc/dovecot.conf # OS: Linux 2.6.18-92.el5 i686 CentOS release 5.2 (Final) base_dir: /var/run/dovecot/ protocols: imap pop3 mail_location: maildir:~/Maildir mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes lock_method: dotlock maildir_copy_preserve_filename: yes mbox_write_locks: dotlock This happens for both pop and imap (however more frequently with imap). Thanks, Mark -- Mark Zealey -- Shared Hosting Team Leader Product Development * Webfusion 123-reg.co.uk, web...

Hello, I have recently changed imap from Courier-imap to dovecot because of serial problems with courier-imap, I have being forced to do it very quickly... and without extensives tests. I have 3 mails servers (freebsd based) behind a load balancer and a nfs mailstore on a netapp. On my first tests I have setup the index into some nfs shared mount, but it seems that some imap clients are

We recently moved all our users from the Washington IMAP server to Dovecot. There has been a substantial improvement in performance, but some users are reporting duplicate messages, and we see 'Stale NFS file handle' errors in the syslog. Does anyone know what would cause this ? The errors relate to the index file, eg. Nov 29 00:49:47 imap-e.ucl.ac.uk dovecot: [ID 107833 mail.error]

Hi there, After being extremely impressed from implementing it in some customer installations, I've decided to migrate our mail infrastructure to dovecot. Being able to have /bin/checkpassword support across the board for pop, imap, and smtp authentication, as well as being able to ditch stunnel for the SSL layer...where were you in 2001?!? :) I have two concerns, the first is about the

...I have a rather big testing environment with four dovecot director frontend instances and four dovecot backend instances. Mailboxes are all in mdbox format and stored on nfs. Indexes are stored locally. dovecot nfs setup for high performance is used (mmap_disable = no, dotlock_use_excl = yes, mail_nfs_storage = yes, mail_nfs_index = no). The remaining problem is, if i disable a backend server and the backend server which took over the connection already has some old index files, this index files aren't updated. If there aren't any index files all is fine and the index files are create...

...But now dovecot does not find the mails in the folder mymbox.gz on the second dovecot server in mdbox format! The relevant part of the dovcot configuration is: # 2.0.16: /opt/local/etc/dovecot/dovecot.conf # OS: SunOS 5.10 sun4v mail_fsync = always mail_location = mbox:~/Mail:INBOX=/var/mail/%u mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = mail_log notify zlib mmap_disable = yes Thank you, -- J?rgen Obermann Hochschulrechenzentrum der Justus-Liebig-Universit?t Gie?en Heinrich-Buff-Ring 44 Tel. 0641-9913054

.... # 2.0.16: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 8.2-RELEASE-p3 i386 auth_mechanisms = plain login auth_username_format = %Lu disable_plaintext_auth = no first_valid_gid = 1000 first_valid_uid = 1000 listen = *, [::] mail_fsync = always mail_location = mbox:~/Mail/:INBOX=/var/mail/%u mail_nfs_index = yes mail_nfs_storage = yes mail_privileged_group = mail mmap_disable = yes passdb { args = session=yes dovecot driver = pam } protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user =...

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

Anyone using either Glusterfs or DRBD in their mail setup? How is performance, manageability? Problems? Tips? Ed W

...nce settings maildir_copy_with_hardlinks = yes maildir_copy_preserve_filename = no # Handling web logins & imap traffic login_processes_count = 16 login_max_processes_count = 2048 max_mail_processes = 4096 mail_max_userip_connections = 2000 # NFS settings mmap_disable = yes fsync_disable = no mail_nfs_index = yes mail_nfs_storage = yes dotlock_use_excl = yes lock_method =fcntl protocol imap { listen = *:10143 ssl_listen = *:10993 imap_client_workarounds = delay-newmail outlook-idle netscape-eoh } ## Authentication processes namespace private { separator = . prefix = Mail. i...

I?m experiencing write activity that?s somewhat different from my previous qmail/courier-imap/Maildir setup. This more outspoken in v.1.1.x than v1.0.x (I?m using Maildir). Write activity is about half that of read activity when measuring throughput. But when measuring operations it?s about 5-7 times as high (measured with zpool iostat on ZFS). I think this might be due to the many small updates

...e-dbox should now be stable - mdbox locking behavior modified. when rebuilding indexes it can no longer fail with deadlocks - fsync_disable=no was renamed to mail_fsync = optimized (default) - fsync_disable=yes was renamed to mail_fsync = never. - added a new mail_fsync = always (basically what mail_nfs_*=yes also did before, but now it can be done without enabling NFS cache flushes) Plus lots of fixes, as usual.

...e-dbox should now be stable - mdbox locking behavior modified. when rebuilding indexes it can no longer fail with deadlocks - fsync_disable=no was renamed to mail_fsync = optimized (default) - fsync_disable=yes was renamed to mail_fsync = never. - added a new mail_fsync = always (basically what mail_nfs_*=yes also did before, but now it can be done without enabling NFS cache flushes) Plus lots of fixes, as usual.

...tup but this seems not 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...

Hi, we have a medium setup (8000 pop and imap users using almost every available client, 800GB of stored mails using maildir on a Celerra NFS server, with index files on local disks, and procmail for local delivery), being served by a Dell PowerEdge 2850 (2GB RAM and dual P4 Xeon 3,2GHz). Our current not-so-high availability setup is based on a similar server with the same setup and a easy