similar to: lock files on mbox using 1.0 stable

Greetings: My outlook users accessing mail via dovecot's imaps have been consistantly getting locked out of their email. It happens about once a week per outlook user. It appears to happen when the are cliking on emails with attachments. When this happens, there are two imap deamons running for that user. I kill both deamons and things start working again. Squirrelmail, thunderbird and

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?

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

dovecot 2.1.x and 2.2.x has "just worked" with a minimal configuration for just about anything I've ever thrown at it. Now, with 2.3.0, there is one user (and only one user) that continually sees horrible delays, which is not surprising given the logs: Error: imap(user)<70175><356C8oljxrCBUppP>: Timeout (180s) while waiting for lock for transaction log file

Hello, we have about 120 servers doing some million mails per day. Most of them use dovecot for pop and imap. In version 1.0.alpha4 we have dovecot-crashes on one or two of the machines in a week where dovecot log says "Panic: key not found from hash" and dovecot dies. We tried version 1.0.beta2 on some machines but with that we have another problem where log says "Error:

Hello everyone, I am testing Dovecot 1.1.3 at the moment to see if I can migrate from UW-Imap(mbox) to Dovecot(maildir). Because I dont' want to influence the production server I installed Dovecot on an ununsed computer with some dummy-testusers using ssl and maildir. Installation was without any problems and everything works fine with one exception: I cannot download some attachments.

This is the trace (gdb) run Starting program: /root/tmp/dovecot-1.0.rc7/src/imap/imap x select inbox Program received signal SIGSEGV, Segmentation fault. mail_index_write_base_header (index=0x80e2a28, hdr=0xaff66028) at mail-index.c:1313 1313 memcpy(index->map->mmap_base, hdr, hdr_size); (gdb) bt #0 mail_index_write_base_header (index=0x80e2a28, hdr=0xaff66028) at

I am running debian etch with dovecot 1.0 rc15 from the debian repository with postfix 2.3 I am using virtual users in a postgreSQL database as taken from the dovecot wiki while making use of the password field for authentication I am using deliver as LDA and I am attempting to use the sieve plugin but try as I might I can't seem to get it working. Am I wrong in thinking that a sieve

> > On 2/16/2009 9:50 PM, Grandy Fu wrote: > >> > I am running dovecot 1.1.10 and 1.1.11 on Solaris 10, mailboxes are in >> > mbox format and served by Solaris 10 NFSv3, the dovecot cache is on >> > local disk. >> > >> > Some of my users always had above nfs error and their mailbox usually >> > very big, over 100M, 400M, or even

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

Hi all, I have a Postfix+Dovecot working in beta/testing; it seems to run very fine, but one beta-tester user says that kmail informs him about frequent desconnections. My dovecot -a shows: # /etc/dovecot.conf base_dir: /var/run/dovecot log_path: info_log_path: log_timestamp: %b %d %H:%M:%S syslog_facility: mail protocols: imaps listen: [::] ssl_listen: ssl_disable: no ssl_ca_file:

We're in the process of moving to Dovecot. We're currently running UW-IMAP live with Dovecot 1.0rc7 on alternate ports for testing. We're set to switch to Dovecot tomorrow morning, and I'm sure I'll have lots of stupid questions once that happens. So I guess you can consider this message an introduction as well as a preemptive apology. Our setup: our mailserver is a

Hi, there! Well, I am new to dovecot, so please be patient with me: I have a virtual server and want to setup simple mail delivery. postfix, saslauthd and dovecot basically work fine. The only open issue is, that (I guess) dovecot doesn't remove the mail when it's retrieved via pop3 from the server. It keeps sending me the same emails again and again. (The mail client (Thunderbird) is

I have recently upgraded to dovecot 1.0.0 on two machines running Scientific Linux 4.3/4.4 x86_64 kernel 2.6.9-22.0.1.EL. The systems come with openssl 0.9.7a and I have installed openssl-0.9.8e. Everything is 64-bit. /usr/local64/sbin/dovecot -n # /usr/local64/etc/dovecot.conf disable_plaintext_auth: no login_dir: /usr/local64/var/run/dovecot/login login_executable:

Hi, i have a big problem with dovecot... PAM auth problem i guess, but don't know how to sort it out... Down the log and the dovecot.conf. Please soemone can tell me what's broken there? Thanks a lot ************************* HERE log ************************* Jun 9 14:49:46 vps dovecot: pop3-login: Can't connect to auth server at default: Resource temporarily unavailable Jun 9

Hi List, last time i did a lot of packaging and installing different versions of dovecot 1.0.x (rc not included ;) )and all was fine. Now a have a little problem. In this case it was an update from 1.0.13 to 1.1.1 Sometime it happens that 1 user out of x (more than 100) got this standardmessage for ~1 or ~2 thousend times in his mailbox (mbox) for example: >From MAILER_DAEMON Mon Sep 18

Hi, I just upgraded from test80 to 1.0alpha1. I wanted to try something new on the lock_method, so I set: lock_method = fcntl, dotlock I got syslog complaints like: IMAP(username): Unknown lock_method: fcntl, dotlock Can one specify multiple file locking mechanisms? If so, what is the syntax (and can the syntax be shown in the comments of the .conf file)? Jeff Earickson Colby College

Dovecot 1.2.10 in Debian, using Dovecot sieve. I have a sieve script, generated by Ingo, that's supposed to mark spam messages as "Seen" and file them into the Junk folder. In part it reads: require ["regex", "body", "imapflags", "fileinto"]; if exists "X-Spam-Flag" { addflag "\\Seen"; fileinto

Hello, I cannot run FTS SOLR engine. OS is debian lenny. I re-compiled debian package (from backports) with --with-solr option. Dovecot loads fts_solr plugin. I know that it loads plugin because if I remove lib21_fts_solr_plugin.so, dovecot does not start. But it does not attempt to communicate with SOLR. Simple check: stop solr tomcat, and open 8080 port in netcat: $nc -l -p 8080 dovecot

Hi All, Our test users re-download the mail they've left on the server when they switch from Qpopper to Dovecot. Qpopper includes the X-UIDL header - X-UIDL: X8V"!E)<"!58?"!"9C"! - on read messages. Any suggestions are appreciated. I've included my dovecot configuration. Thank you, Tristan --- Tristan Tristan Goguen CEO, ILAP? T: 416-250-5600 ext. 205 F: