similar to: Berkeley DB with Dovecot

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

http://dovecot.org/releases/2.0/dovecot-2.0.6.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.6.tar.gz.sig * Pre-login CAPABILITY includes IDLE again. Mainly to make Blackberry servers happy. * auth: auth_cache_negative_ttl default was 0 in earlier v2.0.x, but it was supposed to be 1 hour as in v1.x. Changed it back to 1h. If you want it disabled, make sure doveconf shows it as 0.

http://dovecot.org/releases/2.0/dovecot-2.0.6.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.6.tar.gz.sig * Pre-login CAPABILITY includes IDLE again. Mainly to make Blackberry servers happy. * auth: auth_cache_negative_ttl default was 0 in earlier v2.0.x, but it was supposed to be 1 hour as in v1.x. Changed it back to 1h. If you want it disabled, make sure doveconf shows it as 0.

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

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.

Hello I have a user with 2500+ sub folders. Total mailboxes size is around 6G. (mdbox, dovecot 2:2.0.14) Syncing/Receiving appears to be slow, with outlook 2007. He does not want to switch to an alternative, due to various reasons. I did not find any error logs indicate issues. during idle, imap process appears to loop at adding inotify watches to all folders. I found outlook-idle in wiki,

Hi I've been using courier for some time, but have just built a new box and am using dovecot (V1.2.9), Ubuntu 10.04LTS. I have a question regarding multiple concurrent imap connections and how to get dovecot to behave in the same way that courier does. I have searched the wiki, but find little relevant to my specific issue. Courier-Imap Behaviour If I have thunderbird pointed at the

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

Hi!, I want to use single sign on from Windows with Thunderbird or Outlook using NTLM. Which should be placed in the configuration file for passdb?. Currently I have: passdb { driver = pam } But it generates the following error when trying to check mail: dovecot: auth: pam (pepe, 190 108 101 120): unknown user If I remove imap passdb just does not work and I add at the end of this mail the

I''ve been reading up on Berkeley DB and I''ve been refelcting on the Rails philosophy and it just seemed to me like the two should go together hand in glove. Rails seeks to abstract the programer from squirrely database coding which is great. My only problem is that you''re still left with a large component, namely the databsase server (MySQL, PostgreSQL..etc) which

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()

Did you mislead me Timo? You said search in 1.1+ is faster than 1.0. I'm seeing approximately 20x *slower* search times in 1.2.10. Via Thunderbird, a full body search of my 11,000+ message IMAP folder hosted by 1.0.15 used to take less than 10 seconds. Since upgrading to 1.2.10 the search is taking over 3 minutes, the imap process servicing the client pegging one CPU at 100% for the

Hello everyone, Quoting from Samba Team Blog #2 (25 Sept 2009): "Volker showed how to get more than 700MB/sec from Samba using smbclient and a modern Samba server, which shows what you can really do when you understand the protocol thoroughly and don't feel you have to invent a new one (SMB2 :-)." Would it be possible to get a complete accounting of how this was achieved? Thanks,

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:

I'm considering setting up my own mailserver with Dovecot 2.0 (as soon as it's out) and SSD. I'm debating whether it's worth it or not. I have been running a mailserver with the Dovecot 1.1 train for a couple of years and it's been flawless and amazing. I'm thinking about using either FreeBSD 8.1 w/ZFS or OpenBSD 4.8-beta on a 64 GB or 80 GB SSD (Corsair or Intel) using

I am following the rails book, and arrived to the section about testing. The test database is configured as: test: adapter: sqlite3 database: ":memory:" and I get this error with the simple product test: % ruby test/unit/product_test.rb Loaded suite test/unit/product_test Started E/usr/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.1.0/lib/sqlite3/ errors.rb:94:in

Hello All, Yesterday i put RoR with Locomotive. I am very happy :p. So I follow this tuto (http://developer.apple.com/tools/rubyonrails.html). I used Sqlite. my database.yml # MySQL (default setup). Versions 4.1 and 5.0 are recommended. # # Get the fast C bindings: # gem install mysql # (on OS X: gem install mysql -- --include=/usr/local/lib) # And be sure to use new-style password

The parameters listed for nfs installations (mmap_disable, doctlock_use_excl, mail_nfs_storage, mail_nfs_index) - are they necessary for data integrity, and/or do they compensate for NFS latency and improve performance? My understanding is the indexes are a critical part of a dbox storage, but on the other hand having local indexes is a major performance consideration. Is maildir a

I read in the instructions of Tracks that "upgrading via the rake migrate command is quite a bit more tricky currently with SQLite and SQLite3". Is there any gotcha regarding migrations and SQLite3? -- fxn