On Sep 22, 2007, at 16:55, Timo Sirainen wrote:
On Tue, 2007-08-14 at 22:03 +0200, Michael Guntsche wrote:
Hmm. I guess this could be changed to v1.0 as well:
http://hg.dovecot.org/dovecot-1.0/rev/afb48abd91c0
Hi Timo,
Just installed a patched 1.0.5 version and it works like a charm now
On Sep 14, 2007, at 20:48, Xavier Beaudouin wrote:
(replying to myself)
After a long time, the OS X client say error : "Too Many opened
files".
Seems that OS X has stupidly low number of files that can be opened...
$ ulimit -a
[...]
open files(-n) 256
On my MacBook Pr
On Aug 13, 2007, at 13:49, Timo Sirainen wrote:
What IMAP client do you use? Currently Dovecot works like:
- IDLE starts
- if maildir changes, the new changes are reported immediately
- if client doesn't break from IDLE, continue..
- if maildir changes before maildir_idle_check_interval se
Hello Timo,
On Aug 13, 2007, at 14:15, Michael Guntsche wrote:
Maybe this can be changed that it does not take the interval into
account of it uses inotify, dnotify or kqueue.
My workaround for now is to set the timeout to 1.
I thought about a simple way to implement this
On Aug 13, 2007, at 13:49, Timo Sirainen wrote:
What IMAP client do you use? Currently Dovecot works like:
- IDLE starts
- if maildir changes, the new changes are reported immediately
- if client doesn't break from IDLE, continue..
- if maildir changes before maildir_idle_check_interval se
On Aug 12, 2007, at 18:33, Bruce Bodger wrote:
On Aug 12, 2007, at 11:20 AM, Michael Guntsche wrote:
So my question is can I check that dovecot is actually using inotify?
Which brings me to another question for Timo..
Running Dovecot 1.0.3 on OS X 10.4.10 here. Which --with-notify
Hi,
I recently switched from courier imap to dovecot. With courier I had
a working IDLE setup that informed me immediately when new mail
arrived. With Dovecot it is different, sometimes i get an immediate
result but most of the time it takes a rather long time for the
notification to retu
