[Dovecot] hangs on dovecot test77, mutt
Hi
My toy mail server runs dovecot. My client is mutt, which I use normally use a a remote screen session. I normally connect to imap locally:
account-hook imap://localhost/ 'set tunnel="/usr/local/bin/imap-local"'
After a long frustration from the new mail notification in 0.99, I have decided to bite the bullet and try the -test series. Ever since I have not had stable mutt sessions.
Occasionally mutt hangs on the imap connection. Usually when openning a new mailbox. But sometimes even when closing an existing mailbox. Occasionally mutt will even crash (which is annoying, but certainly not a bug of dovecot).
How do I debug this?
--
Tzafrir Cohen | tzafrir@jbr.cohens.org.il | VIM is
http://tzafrir.org.il | | a Mutt's
tzafrir@cohens.org.il | | best
ICQ# 16849755 | | friend
On Fri, Aug 12, 2005 at 06:38:15PM +0300, Tzafrir Cohen wrote:
Hi
My toy mail server runs dovecot. My client is mutt, which I use normally use a a remote screen session. I normally connect to imap locally:
account-hook imap://localhost/ 'set tunnel="/usr/local/bin/imap-local"'
imap-local simply sets MAIL:
#!/bin/sh
# imap-local: run dovecot's imap as your user
MAIL='maildir:~/Maildir'
exec /usr/lib/dovecot/imap
After a long frustration from the new mail notification in 0.99, I have decided to bite the bullet and try the -test series. Ever since I have not had stable mutt sessions.
Occasionally mutt hangs on the imap connection. Usually when openning a new mailbox. But sometimes even when closing an existing mailbox. Occasionally mutt will even crash (which is annoying, but certainly not a bug of dovecot).
More details: System is Debian 3.1 (Sarge). Kernel 2.6.8-2-686. glibc 2.3.2.ds1-22 (the default).
How do I debug this?
Any way to tell it to log all imap commands to a log file? Or any other way to isolate the problem?
--
Tzafrir Cohen | tzafrir@jbr.cohens.org.il | VIM is
http://tzafrir.org.il | | a Mutt's
tzafrir@cohens.org.il | | best
ICQ# 16849755 | | friend
On Sat, Aug 13, 2005 at 07:10:53AM +0300, Tzafrir Cohen wrote:
Any way to tell it to log all imap commands to a log file? Or any other way to isolate the problem?
If you build Dovecot with the --with-rawlog flag, then you can put a dovecot.rawlog directory in the user's home directory to capture IMAP events.
(This is described in the wiki, and also mentioned at http://www.dovecot.org/bugreport.html.)
-- Jim Tittsler http://www.OnJapan.net/ GPG: 0x01159DB6 Python Starship http://Starship.Python.net/crew/jwt/ Mailman IRC irc://irc.freenode.net/#mailman
On Sat, 2005-08-13 at 14:29 +0900, Jim Tittsler wrote:
On Sat, Aug 13, 2005 at 07:10:53AM +0300, Tzafrir Cohen wrote:
Any way to tell it to log all imap commands to a log file? Or any other way to isolate the problem?
If you build Dovecot with the --with-rawlog flag, then you can put a dovecot.rawlog directory in the user's home directory to capture IMAP events.
(This is described in the wiki, and also mentioned at http://www.dovecot.org/bugreport.html.)
Well, yes, except when running imap binary directly the rawlog needs to be executed also:
#!/bin/sh
# imap-local: run dovecot's imap as your user
MAIL='maildir:~/Maildir'
exec /usr/lib/dovecot/rawlog /usr/lib/dovecot/imap
In 1.0-tests --with-rawlog option doesn't exist anymore, the rawlog binary is always built.
On Fri, 2005-08-12 at 18:38 +0300, Tzafrir Cohen wrote:
Hi
My toy mail server runs dovecot. My client is mutt, which I use normally use a a remote screen session. I normally connect to imap locally:
account-hook imap://localhost/ 'set tunnel="/usr/local/bin/imap-local"'
Also do you use any other clients to connect to it? Especially using TCP connections?
If Dovecot prints some errors, does mutt show them or does it just ignore them? Maybe execute it through shell and add some 2>~/dovecot.log to see if anything gets logged?
participants (3)
-
Jim Tittsler
-
Timo Sirainen
-
Tzafrir Cohen