Hi I dont uderstand your problem, but did you try to debug one "failing connection". You can log a full imap session using this way : To enable protocol logging, simply create a directory in /var/lib/imap/log with the user's name you wish to log. Ensure, of course, that this directory is writable by the user Cyrus runs as. Cyrus will create files in this directory with the name of the process ID under which it runs (which changes per connection due to the forking server model it uses). Then you should be able to search the log for some imap inconsistencies. Regards On 10/15/07, Ian G Batten <ian.batten@xxxxxxxxxxxxxx> wrote: > > On 12 Oct 07, at 1901, Ian G Batten wrote: > > > I've just brought up our 2.3.9 installation. My logs are filled with > > `idled: unrecognized message: 3', happening around the time of > > login. Should I worry? > > Tracked that one down. In 2.2 you need --with-idle=idled. With 2.3 > you need --enable-idled. I compiled 2.3 with the same config deck as > 2.2, and then installed it into the same partition. So I had the 2.2 > idled. Which worked, astoundingly enough, but logged a lot of > problems with things it didn't understand. > > Anyroadup, ~1000 users on a T2000, load average is below 1.0, zfs'd > metadata partitions (compression=on, atime=off) are taking most of > the load with the non-metadata partitions over NFS being treated very > gently. > > ian > > ---- > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ > Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > -- Alain Spineux aspineux gmail com May the sources be with you ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
