similar to: nfs locking issues...

I've been testing alpha4, and every once in a while my client (Thunderbird 1.5 RC1) tells me the dovecot isn't a valid IMAP4 server. This is usually (maybe always) when I first bring up the client up. If I just ask the client to get the mail again, it does so happily (without any errors). I must say I found dovecot as a pleasant surprise. We have been using UW. Which didn't

Timo, What are you thoughts on when we might see 1.0? Thanks, John -- John Gray gray at agora-net.com AgoraNet, Inc. (302) 224-2475 314 E. Main Street, Suite 1 (302) 224-2552 (fax) Newark, De 19711 http://www.agora-net.com

Hello, My user's imap folder locations are a mess. Some have them in /home/username/mail but a lot of them just have them in /home/username. So I need to have dovecot's base imapdir pointed directly at the user's homedirs. My problem now is that a lot of users have many links in their homedirs. Some even have circular links, such as: /home/username/foo/foo1/foo2/foo3/foo4 ->

I've read the wiki and other resources on how to connect Vonage / Voicepulse and all these other services to Asterisk... We are attempting a connection to a Lucent iMerge. Lucent has told us that it won't work - but we feel confident that it will. Has anyone worked with the Lucent iMerge - or would be willing to help lend a hand? It is capable of H323 / MGCP. Even if I could make the

Hi folks, someone using Debian? I need the init script, if you please :) Thanks for your support Regards Andrea

Is there a plan to upgrade the stable package from 1.0-rc15?

Hello, I work for an organization that uses a Secure Dovecot server for messaging, and recently we've had to undergo some security screenings for PKI compliance (credit card industry standards). However, the screening returned to us a failure due to the following reason (attributed to our Dovecot server, which runs on port 993 and is the only "open" port on our firewall): Synopsis

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

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

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

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

/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

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

How does IMAP lock the /var/spool/mail/user file? Here's my problem: I'm writing a script to expire old or oversize mail through a series of archive folders. I don't want to take the whole server down to do this, nor does it seem like I would have to lock the user out entirely if I can manage to emulate the locks correctly. I am able to lock /var/spool/mail/user (and ~user/mail/*)

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

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

Upgrading to 0.9.0, I have the following error. Anybody? c:/ruby/lib/ruby/gems/1.8/gems/ferret-0.9.0/lib/ferret/index/term.rb:35:in `<=>'': undefined method `<=>'' for :id:Symbol (NoMethodError) from c:/ruby/lib/ruby/gems/1.8/gems/ferret-0.9.0/lib/ferret/index/term_infos_io.rb:263:in `get_index_offset'' from

Clearly I'm missing something about --link-dest; I know it works because rsnapshot is doing the right thing on this system, but it's not on another system, and I'm trying to troubleshoot that. The first step is to be able to verify that --link-dest works on it, but I can't even get it to work in an known-good environment --- no matter how I specify the args to it, it's

Hi there... Having updated to 1.0.beta1, I for a while thought a bad bug with IDLE handling that caused new mail in INBOX not to appear when using Mozilla Thunderbird has been solved. Although I can not reproduce one kind of problem anymore, after a short while it again appears that one does not always see one's new mail with Thunderbird. I can not consistently reproduce the bug, but

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,