Re: Howto debug problems with an imap server?
- To: mutt-users@xxxxxxxx
- Subject: Re: Howto debug problems with an imap server?
- From: Kyle Wheeler <kyle-mutt@xxxxxxxxxxxxxx>
- Date: Wed, 12 Mar 2008 18:33:08 -0500
- Comment: DomainKeys? See http://domainkeys.sourceforge.net/
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=memoryhole.net; h=date: from:to:subject:message-id:references:mime-version:content-type: in-reply-to; q=dns/txt; s=default; bh=yI2YU2o7xfOOElp0kVypF/jBL+ s=; b=VtNZyl6bsfUMB7tmKHHg2odHE4gaOFhJB3oh4DIiVxHECszYbGg2zIzbN0 h8AHuYJbOJ7grBtv+gjE7oyilUv6wqD+wBulCZdMITy+sbPqCHGY4g/pxS//ekrF MV0kADydGJZ9RtNbdMRAJk3rAXtcdpW9MnbzqDLun9nqHCk4Y=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=memoryhole.net; b=khCst7pFUS1dmWHJQTt2U80mg/z65gU3iiTHwRgp2KC+uOhbn0BTr9Vl8uOouNlA9ttW5u+wYDHbGy4wXXNsgemlcacC6qtdFHJCyh6TbQ9dakGfX4ryMIhHXkvsq6lQ8UVrKcfHfZWASsDVhxmDuPsfhhwC5A10F1JbHlnjOVU=; h=Received:Received:Date:From:To:Subject:Message-ID:Mail-Followup-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:OpenPGP:User-Agent;
- In-reply-to: <20080312230646.GA9120@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- List-post: <mailto:mutt-users@mutt.org>
- List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-users"
- Mail-followup-to: mutt-users@xxxxxxxx
- Openpgp: id=CA8E235E; url=http://www.memoryhole.net/~kyle/kyle-pgp.asc; preference=signencrypt
- References: <20080312192351.GC4549@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <20080312204148.GQ3232@xxxxxxxxxxxxx> <20080312230646.GA9120@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Sender: owner-mutt-users@xxxxxxxx
- User-agent: Mutt/1.5.17 (2008-02-27)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday, March 13 at 12:06 AM, quoth Andreas Pakulat:
> Aah, thanks. Looking at the output I don't see much, except the
> following (towards the end of the file):
> a0038 STATUS "Spam" (UIDNEXT UIDVALIDITY UNSEEN RECENT MESSAGES)
> 4< a0038 OK done
> mutt_num_postponed: 0 postponed IMAP messages found.
> cmd_new: IMAP command queue full
Hmmmm, that last part there is suspicious. Doubtless the reason that
mutt hangs is because its command queue is full. The real question,
though, is why that queue isn't emptying. I *think* that queue should
empty as responses come back from the server, so my guess would be
that mutt somehow isn't associating responses with the original
command that sent them and so remains waiting for answers to the
commands its already sent. Eventually it can't keep track of more than
X number of commands, and so it refuses to send any more until it gets
responses back to the commands its already sent.
I think you should probably file a bug report (http://bugs.mutt.org),
and include a longer snippet of your debug log when you do (showing
several of the commands and responses leading up to the "queue full"
line).
~Kyle
- --
The government is like a baby's alimentary canal, with a happy
appetite at one end and no responsibility at the other.
-- Ronald Reagan
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iEYEARECAAYFAkfYaDQACgkQBkIOoMqOI16hogCffeDTEjDP01IbDhicnQo4jXyD
qJgAniNqWoVe0/6SVqcn2Rw/goyX743b
=cxDv
-----END PGP SIGNATURE-----