similar to: NFS, IDLE, and index locking

I'm experiencing some problems similar to those described in http://dovecot.org/list/dovecot/2012-July/137250.html except with 2.0.9. Adding http://dovecot.org/list/dovecot/2012-July/084906.html to the main config didn't seem to help, nor did setting the list of director and backend servers to just the system itself. I get a banner connecting to port 143: [root at retr01 log]# telnet

Hi, I've upgraded from 1.0.7 to 1.1.3. When I did this, my Thunderbird lost its brain and did not show some subscribed folders. squirrelmail also seemed to have issues. Applemail and mutt were fine. The configuration output is below. Hopefully this is just me and just random bizarreness. There wasn't a problem in 1.0.7 but I could have been caught in mid-upgrade. Thunderbird did not

Hi there, I've been seeing this error in our logs quite frequently on our nfs storage (v3): 2008-11-10T13:24:26+00:00 mail8 dovecot: IMAP(XXX at YYY.com): nfs_flush_fcntl: fcntl(/var/spool/mail/XXX/Maildir/dovecot.index.cache, F_RDLCK) failed: No locks available Which is because we don't run lockd on our servers. Why is dovecot trying to use fcntl() ? I explicitly set it to use dotlocks

Hi, i'm in the process of evaluating dovecot. 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

Hi, Up until yesterday, our environment which consists an NFS maildir file store with multiple front end servers, was working fine. We've verified that the server clocks and machines clocks are in sync. Starting yesterday afternoon, We are getting ~850 log entries of the form 'Timeout while waiting for lock for transaction log files' or 'Our dotlock file was modified,

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

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

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

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

Hello, can dsync convert from compressed mbox to compressed mdbox format? When I use compressed mbox files, either with gzip or with bzip2, I can read the mails as usual, but I find the following errors in dovecots log file: imap(userxy): Error: nfs_flush_fcntl: fcntl(/home/hrz/userxy/Mail/mymbox.gz, F_RDLCK) failed: Bad file number imap(userxy): Error: nfs_flush_fcntl:

I'm running dovecot 2.0.16 on FreeBSD 8.2 with the mail spool and indexes on an NFS server. Lines like the following keep appearing in syslog for access to each mailbox: Error: nfs_flush_attr_cache_fd_locked: fchown(/home/philk/Mail/Deleted) failed: Bad file descriptor This is coming from nfs-workarounds.c line 210, which tracing back seems to be coming from the call to mbox_lock on

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

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]

We recently started upgrading OpenSSH on our Sol8 systems and we've run into a problem were we can run commands on a remote system since we installed 3.7.1p1. The debug output from sshd is attached below. We use PAM in our environment, and have since 2.9.9p2. I think most of the systems were running 3.4p1 prior installing 3.7.1p1 and they were working - the only thing we replaced was

I ran into a weird problem yesterday where Putty can't connect to my OpenSSH/Sol box (and still can't ever since). On the Putty side I get the error message: "internal fault: chaos in SSH 2 transport layer" I've attached the "sshd -d -d -d" syslog output. Any ideas what's going wrong here? From a layman's point of view, it would appear that Putty and

Hello All, We are struggling to find a solution to a problem we are encountering with a load-balanced email setup. Currently, we have a Coyote loadbalancer, and 3 Postfix/Dovecot nodes that then get their information from a mysql database. The problem is that after a couple weeks, we start seeing NFS locking issues occur, which then takes email completely down, requiring a site visit to

I've got a weird split setup where POP3 is currently handled by Courier (courier-imap-3.0.2 distribution), and IMAP is currently handled by the RHEL 5 version of Dovecot (1.0.7) I'm trying to figure out a way to convert the POP3 UIDLs (in cases where the courierpop3dsizelist is newer than dovecot-uidlist, at least) to something that Dovecot will read, or to configure Dovecot's pop3 to

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

Hi, I am setting up a fileserver in an AD domain, using Samba 3.0.21b under Solaris 9. An Openldap server (version 2.3.17) is used fot the idmap backend. Following the Samba HOWTO Collection, chapter 6, I used the statement ldap idmap suffix = ou=idmap,dc=uppsala,dc=se in my smb.conf. This doesn't work. When starting winbindd I get the following in the log: [2006/02/15 10:31:14, 3]

I have dovecot version 2.0.9 I am confused about this article http://wiki2.dovecot.org/Errors/ChgrpNoPerm my mail_location = mbox:~/mymail:INBOX=/var/mail/%u So my inbox is at var/mail/ and my imap folder is /home/user/mymail The problem is /var/mail (Owner is useraccount and the group us mail) , and here comes the problem Dovecot keeps trying to chown the imap folder inside the