similar to: fcntl error

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

Hello, I have a question regarding mailbox locking and hope any one can help me to better understanding the locking of mbox My Postfix lock option is fcntl dotlock mailbox_delivery_lock = fcntl, dotlock virtual_mailbox_lock = fcntl, dotlock My Dovecot lock option is fcntl only mbox_write_locks = fcntl mbox_read_locks = fcntl now, when user is download a large mail (20 MB) for example,

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

I have Dovecot 1.0 in trial use by the IT staff, and have some locking questions Background, the mail server runs procmail, sendmail and NFS exports the user homedir and mailbox to a) a login shell host and b) a mailing list services host. It runs UWIMAP on the usual ports and dovecot on a arbitrary port number. Because of concern with NFS and file access contention. I have the following

Hello, I'm using dovecot as a mail relay so that I can back up my providers IMAP mail locally. I'm impressed how easy this was to set up, but I'm having a quirk that I would like help with, if possible. There are many weak links in my set-up chain, if you will, but I think I've narrowed the problem. I'll describe my set-up anyway. I'm running dovecot 1.1.4 on ubuntu

Hi all, I have some machines running FreeBSD and dovecot deployed. User's home dir is on NFS mount and I've found that dovecot only works with dotlock file locking mechanism, fcntl and flock failed. Now it causes problem with thunderbird (thunderbird is cachine connections) waiting forever and I noticed that dovecot is trying to acquire a lock but unsuccessful since the lock file is in

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

Hi my last post got no replies so i am trying again. FC3 dovecot 1.0 stable, 1 user has a lock file using mbox under /var/spool/mail/username from the lock file the pid files are File Descriptor Type File size Inode Path Current dir Directory 4096 6426371 /home/domain/domain127 Root dir Directory 4096 2 / Program code Regular file 1212428 1229832

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.

i'm working with exim 4.60, with mbox, and dovecot dovecot-1.0.beta7, and filesystem quotas default_mail_env = mbox:~/mail::INBOX=%h/mbox:INDEX=/tmp/%u lock_method = dotlock fcntl mbox_read_locks = dotlock fcntl mbox_write_locks = dotlock fcntl The home of users is /home/usuaris/user Where place dovecot the lock file?

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

Hi there, We're using Dovecot version 1.0.7 and Postfix, and since upgrading our Linux box we're getting this in the maillog: Nov 8 07:49:11 server1 postfix/local[27901]: 04B8E7081DA: to=<xyz at xyz.com>, orig_to=<abc at abc.com>, relay=local, delay=19, delays=0.07/0/0/19, dsn=4.2.0, status=deferred (cannot update mailbox /var/spool/mail/abc for user abc. unable to lock

/etc/postfix/main.cf.default: mailbox_delivery_lock = flock, dotlock Is flock equivalent to dovecot's fnctl locking? For mbox what type of locking settings should I be using? (No NFS, only local filesystem.) Warren Togami warren at togami.com

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

Hi Slight problem - linux 2.4 running dovecot, Solaris 2.8 home directory server. Full lockd support etc. I had to make the following code patches (at end of mail for clarity) to get dovecot to read the users mbox files at all. 1) fcntl with F_SETLKW will not work against a Solaris 2.8 server as proved with a small test program. Other forms of fcntl (ie F_SETLK) are OK. I noticed there are

http://dovecot.org/tools/nfstest.c I wrote a test utility that tests different ways to flush NFS attribute cache and data cache. Please test in your NFS setup and show me the results, so I can make Dovecot v1.1 works well with NFS. Run the test several times (3 should be enough) to make sure the output stays the same, because the attribute cache flushes might incorrectly say "OK". And

Dear Colleagues, I use exim's appendfile transport, procmail and a local mutt on my system, they all (to my knowledge) use lockfiles when working with mboxes. However, `doveconf | grep lock` says dotlock_use_excl = yes lock_method = fcntl mail_max_lock_timeout = 0 mbox_dotlock_change_timeout = 2 mins mbox_lock_timeout = 5 mins mbox_read_locks = fcntl mbox_write_locks = dotlock fcntl

I'm using dovecot 2.2.24 on FreeBSD 10.3. I'm working on converting users from maildir to mdbox, for the usual reasons. I have converted some test users and they generally work fine. But when I run "doveadm mailbox status" I get a Panic if I ask for the vsize field (or "all"), but other fields work fine. For example: # doveadm mailbox status -u bubbacheex3

Folks - I've been using Dovecot for some time now, but have only recently upgraded to 1.0alpha4. I'm struggling to get my configuration right and I'm seeing some truly bizarre issues. My Setup: Solaris 2.8 / Thunderbird / Procmail / Dovecot 1.0alpha4 My mail setup is only for me, so Dovecot runs at an odd port and under my userID. All my mail is in my home directory, which

Hi, About a week ago I upgraded our reasonably heavily loaded mail servers from a pretty recent courier version to dovecot-1.1rc10. IMAP performance on dovecot is amazing, however POP3 performance is worse than courier :-( I have uploaded some munin graphs taken today to http://linweb.atlas.pipex.net/dovecot/; the dovecot server is handling about 2000 pop logins/sec and 300 imap sessions (but