similar to: Migrating from NetApp to ZFS

Hello, In the past we've had 4 loadbalanced servers configured with courier pop3 and dovecot handling respectively POP3 and IMAP connections. These 4 servers have a shared NFS storage on a Netapp FAS3220 controller with SAS disks. This setup is handling 50 POP3 sessions per second without any problems. Now we're installing 6 new loadbalanced servers to do the same job on the same

[ Wish there was a generic, active Linux "storage" mailing list out there -- something other than the kernel lists I mean ] To frame the discussion, we use VMware ESX (vSphere) quite a bit with NFS datastores. Often times with NetApp, but lately, more often with Solaris 10 + ZFS + SSD's for ZIL (intent log or write cache). The ZIL lets us use synchronous writes (safer) without

Hi Timo, dovecot 1.2.0 is great! Faster and more stable on mboxes that 1.1.x by far... good job :-) Today I stumbled over a strange problem when I tried to subscribe an existing Mailbox (mbox), which doesn't work. Thunderbird IMAP log -------------------- 9932[4124558]: 40f3498:imap.fh-trier.de:A:SendData: 11 subscribe "Mail/Archiv/1998" 9932[4124558]: ReadNextLine

For the record/archive, so some other unfortunate dovecot implementer won't spend weeks figuring out this particular way dotlocks can have problems... here is what was trashing our dotlocks Basically, I was seeing this: May 14 15:59:58 mercury mail:warn|warning dovecot: IMAP(sdean): Our dotlock file /var/spool/mail/sdean.lock was deleted (kept it 1 secs) > May 14 15:59:58 mercury

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.

Hi, In our dovecot setup we use 3 different config files. One for maildropping(sieve), one for dovecot/imap on standard ports with ssl config and one for dovecot/imap on standard ports+1 with a different ssl certificate. Currently the client using the standard port+1 config wants to make use of shared folders, but the thing is that the current namespace separator in all configs is '.'.

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

Hello, is dotlock supposed to work with NFS? I noticed that the default-locking method causes problems even with nfslockd started. Regards Marten

We are in the process of migrating away from Courier-IMAP/POP3 and Maildrop. I want to use Dovecot (LDA, IMAP, POP3). During my testing, it has worked great except for dotlocking on the dovecot-uidlist file. The problem: When a delivery is being made with deliver and a mail client has the mailbox open (Thunderbird in this case), neither Thunderbird or deliver can get a dotlock on the

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 30 Nov 2015, Frido Otten wrote: > In our dovecot setup we use 3 different config files. One for > maildropping(sieve), one for dovecot/imap on standard ports with ssl > config and one for dovecot/imap on standard ports+1 with a different ssl > certificate. Currently the client using the standard port+1 config wants > to make

Hello, I'd like to make sure my understanding of the mbox locking strategy is correct : - "mbox_dotlock_change_timeout" directive : a process seeing that an already locked (by another process) mbox he want to access hasn't change for this amount of time, allows himself to override the lock ? If it's using fcntl, is it only possible to override ? -

Hello, Running dovecot 1.1.6 on centOS 5 and RHEL 5. With the settings: pop3_lock_session = yes mail_privileged_group = mail mail_location = mbox:~/:INBOX=/var/spool/mail/%u mbox_read_locks = fcntl mbox_write_locks = dotlock fcntl and /var/spool/mail permissions: drwxrwx--x 2 root mail 4096 Nov 19 10:16 mail/ Trying to connect via POP3 results in this error: --- Nov 19 09:31:01

We're running dovecot 2.3.10 on two different servers (two different environments). Both very similarly configured (sendmail and procmail for mail delivery); same OS and patch levels. One environment has nearly 10,000 users and hasn't seen problems. The other environment has just a handful of users, but one user is very active with email and has a fairly complicated procmail

A Debian developer had this to say: > >> Files in the above dir are group mail, and the dir is group mail. However, > > > all binaries in /usr/lib/dovecot are root/root. I have set them all to g+s, > > > and group mail, and now the imap process can lock the INBOX. > > > > > imap should be the only one that needs to be setgid mail. > > Actually,

Hello Timo, I'm running dovecot-1.0.rc15 (imap and pop) postfix-2.3.5,1 procmail-3.22_6 (which is my LDA) on FreeBSD 6.1-STABLE I'm still using the mbox format (I'm planning to migrate to Maildir soon), mailboxes are on an NFS filesystem. I regulary see stale dotlocks files (either from dovecot (29 bytes, hold the pid of the process) or procmail (1 byte) and processes

Hello, I'll soon have to migrate our samba shares to a netapp filer (not my decision). Currently the shares are on an xfs filesystem and served by samba 3.5.2, which is also the domain controller (a role that it will maintain, only the shares are being transferred) and sama/unix users are in ldap. The filer is in the domain and uses ldap to map user ids and that seems to work. Samba maps the

Hello list, someone (actually neil perrin (CC)) mentioned in this thread: http://mail.opensolaris.org/pipermail/zfs-discuss/2009-December/034340.html that is should be possible to import a pool with failed log devices (with or without data loss ?). >/ />/ Has the following error no consequences? />/ />/ Bug ID 6538021 />/ Synopsis Need a way to force pool startup when

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

There are three applications that have their mitts on files on my mail server, which is running AIXV5.3 and UWIMAP and mbox format. The mail folders and INBOXES are native to that machine, but also are NFS exported to a login server and a mailing list server. All three machines are running the lockd daemon. Everybody wants to lock differently 1) procmail (delivering for sendmail), which