ram wrote: > On Mon, 2009-03-02 at 09:15 -0600, Dan White wrote: > >> You could enable telemetry logging, which should help to rule out a >> problem with the client. >> >> > > How do I do that ? > > > See: http://cyrusimap.web.cmu.edu/imapd/overview.html You create a folder with the same name as the user connecting, underneath the cyrus log directory. Make sure you set appropriate permissions on the directory so that cyrus can write to it. Telemetry logging logs each interaction between the client and the server, except for authentication, which isn't logged. Also, if you're receiving a pop lock response, that probably does not get logged in telemetry logging either, so you should also monitor your syslog for connection attempts. You want to verify that the client is sending a 'quit' at the end of each telemetry log. - Dan ---- 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
