similar to: body search very slow since upgrade from 1.0.15 to 1.2.10

Upgraded from Debian Dovecot 1.0.15 to Debian Dovecot 1.2.10-1~bpo50+1. I use Postfix local delivery to and Dovecot mbox. As per upgrade directions, I stopped dovecot processes and deleted all dovecot.index.cache files in /home/%user/mail/.imap. Performed upgrade to 1.2.10-1~bpo50+1. Modified new dovecot.conf for my environment. Started dovecot. Problem: Instantly noticed in TB 3.0.1 Win32

With 1.0.15 my configuration I a single dovecot-auth process, which is what I want now. Since upgrading to 1.2.10 I have two such processes: root 16992 16990 0 Feb15 ? 00:00:00 dovecot-auth root 16997 16990 0 Feb15 ? 00:00:00 dovecot-auth -w I can't seem to tweak dovecot.conf to get this down to one auth process again. I've tried setting each of these below to 0,

System: Debian 5.0.4 Lenny Kernel: custom 2.6.31.1 built from kernel.org source Dovecot: 1.0.15-2.3+lenny1 Available: 1.2.9-1~bpo50+1 Mailbox format: mbox Storage location: /home/$user/mail/ on ext2 fs Delivery: Postfix 2.5.5 local to /var/mail/$user As you can see Debian has a backport package of Dovecot 1.2.9 available to Lenny users, and it appears it is a big jump forward in terms of

Greetings everyone, I'm new to the list as of today. I just installed Dovecot a couple of days ago for the first time, Debian Lenny Dovecot v1.0.15-2.3. So far I'm pretty impressed. I'm using mbox format with Dovecot auto-deciding to place mail in user home directories, which is great. It works very well with the Win32 Thunderbird 3 client over a small basic 100FDX switched net.

Taking a survey. 1. How many of you have a remote site hot backup Dovecot IMAP server? 2. How are you replicating mailbox data to the hot backup system? A. rsync B. DRBD+GFS2 C. Other Thanks. -- Stan

With 1.2.11 and mbox storage, the delay time in pulling new mail headers to the client from imap folders seems to be directly proportional to mailbox size, regardless of the number of new messages. At present, if the mailbox is large, pulling new headers is rather painfully slow. Is this expected behavior? Especially given that the client already has all the "old" mails in the folder

Hi all, We've just provisioned a new cluster of dovecot nodes running Centos and Dovecot 1.0.15 (we needed to match the original configuration, we're upgrading to 1.2 next week!). The nodes are currently equally allocated (50/50 split) to IMAP and POP3, with the intention to move them into a single cluster hosting both services in the next month. All the servers are of identical

I would not have expected this upon implementing sieve. And I really need to get around this limitation. LDA has no problem writing to these large mbox files. Why does sieve have a problem with them? This is very odd. May 10 17:45:04 greer dovecot: deliver(stan): write() failed with mbox file /home/stan/mail/1-Debian-Users: File too large May 10 17:45:04 greer dovecot: deliver(stan): write()

Per the instructions here http://wiki.dovecot.org/LDA and here http://wiki.dovecot.org/LDA/Postfix I set postmaster_address = postmaster at hardwarefreak.com in /etc/dovecot/dovecot.conf and mailbox_command = /usr/lib/dovecot/deliver in /etc/postfix/main.cf When I restart dovecot I get this: [07:17:00][root at greer]/etc/dovecot$ /etc/init.d/dovecot restart Restarting IMAP/POP3 mail server:

Following these instructions: http://wiki.dovecot.org/Plugins/Zlib I enabled zlib and restarted Dovecot. I made a backup copy of a 68MB mbox file and moved it to a non mail directory. The mbox file is an existing TBird IMAP folder in my UNIX user mail directory. It is an archive of a defunct mailing list. It was a regular IMAP folder prior to attempting this. I was able to access all emails

I've Google'd to exhaustion and can't seem to find an answer to my problem. I'm not sure if the problem is TBird 3 or my Dovecot setup. The basic problem is that when I launch TBird and it grabs messages upon startup, it takes forever to supposedly pull them down. Once it's got them they sort relatively quickly into the proper IMAP (dovecot) folders. I don't use sieve

> From: Stan Hoeppner <stan at hardwarefreak.com> > Subject: Re: [Dovecot] SSD drives are really fast running Dovecot > > > Yes. Go with a cluster filesystem such as OCFS or GFS2 and an inexpensive SAN > storage unit that supports mixed SSD and spinning storage such as the Nexsan > SATABoy with 2GB cache: http://www.nexsan.com/sataboy.php I can't speak for

Dear All, Is there any easy way to upgrade Dovecot like yum command? Or I have to delete the current and install the new version then change the setting?> I will appreciate if you can tell me the steps please? Best Regards Arif --- On Fri, 1/10/10, dovecot-request at dovecot.org <dovecot-request at dovecot.org> wrote: From: dovecot-request at dovecot.org <dovecot-request at

From: http://wiki.dovecot.org/Plugins/FTS "You could also build a cronjob to index users' mailboxes once in a while (by selecting each mailbox and issuing a SEARCH TEXT xyzzyx command)." Has anyone written a script to perform the above? If not, how would I do this? Would I write a shell script to telnet to the IMAP port and then issue the commands? Can this be done with a bash

Murray Collingwood put forth on 4/20/2011 8:29 PM: > Hi Stan > > I only have the one account on this server, everything else is relayed > elsewhere. If this is an SMTP relay server, I'm surprised you bothered to install an IMAP server at all. It would have been easier to simply alias postmaster@ to another account on another machine where you do store mailboxes. I.e. simply

Samba 3.2.5 on Debian Lenny From: http://www.samba.org/samba/docs/server_security.html "Samba is able to limit the number of concurrent connections when smbd is launched as a daemon (not from inetd). The 'max smbd processes' smb.conf option allows Administrators to define the maximum number of smbd processes running at any given point in time. Any further attempts from clients to

Stan, Thanks for the reply. In our case we have actually already done most of the work you suggested to no avail. We had rebuilt two new ntp servers that sync against two stratum 1 sources, and all our nfs clients, regardless of using dovecot, sync to those two machines. You bring up the difference between bare metal and hypervisor, and we are running these machines on vmware 4.0. All the

I've received a bunch of these blackberry backscatter messages over the past week and have been unable to determine which list user is the cause of this. Whoever is forwarding your email to the blackberry address below, please fix the situation. It's becoming really annoying receiving these backscatter bounces that give no clue as to what the nature of the problem is. Thanks. Your

I went to the site to subscribe again and ended up watching some of Jeremy's Google interviews. I particularly enjoyed the interview with James and the bow tie lesson at the end. :) So anyway, I recently upgraded my home network to end-to-end GbE. My clients are Windows XP SP3 w/hot fixes, and my Samba server is 3.5.6 atop vanilla kernel.org Linux 3.2.6 and Debian 6.0.6. With FDX fast

Hi Timo, Any chance the mbox/mdbox writer code could be modified to do physical preallocation on files to help avoid file(system) fragmentation? Constantly appending a file is the prime recipe for causing fragmentation, and mbox is notorious for this--not a fault of Dovecot but the nature of the mbox beast. Obviously maildir doesn't have such a problem, but some (many?) of us still prefer