From: egallego@babel.ls.fi.upm.es (Emilio Jesús Gallego Arias)
To: ding@gnus.org
Subject: Re: How to debug hangs during message fetching
Date: Wed, 23 Feb 2011 03:18:14 +0100 [thread overview]
Message-ID: <87zkpnv6hl.fsf@babel.ls.fi.upm.es> (raw)
In-Reply-To: <87tyg28bp0.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Could you try evaling
>
> (nnimap-request-list "dovecot")
>
> and see whether that works at all?
When I press g in the "bad" version, the equivalent of
(nnimap-request-list "dovecot") happens. In the form of:
03:15:58 4013 LIST "" "*"
03:15:58 4014 SELECT "INBOX"
03:15:58 4015 UID FETCH 1:* FLAGS
03:15:58 4016 EXAMINE "INBOX"
03:15:58 4017 UID FETCH 1:* FLAGS
03:15:58 4018 LIST "" "*"
03:15:58 4019 SELECT "INBOX"
03:15:58 4020 UID FETCH 1:* FLAGS
03:15:58 4021 EXAMINE "Spam"
03:15:58 4022 UID FETCH 42:* FLAGS
03:15:58 4023 EXAMINE "Sent"
03:15:58 4024 UID FETCH 1:* FLAGS
03:15:58 4025 EXAMINE "INBOX"
03:15:58 4026 UID FETCH 33181:* FLAGS
03:15:58 4027 LIST "" "*"
03:15:58 4028 SELECT "INBOX"
03:15:58 4029 UID FETCH 1:* FLAGS
03:15:58 4030 EXAMINE "INBOX" (QRESYNC (1240303625 27))
03:15:58 4031 LIST "" "*"
03:15:58 4032 SELECT "INBOX"
03:15:58 4033 UID FETCH 1:* FLAGS
03:15:58 4034 UID FETCH 287 (UID BODY.PEEK[HEADER] BODY.PEEK[1])
03:15:58 4035 EXAMINE "Sent" (QRESYNC (1252931194 1))
03:15:58 4036 EXAMINE "INBOX" (QRESYNC (1252931192 88))
03:15:58 4037 LIST "" "*"
03:15:58 4038 SELECT "INBOX"
03:15:59 4039 UID FETCH 1:* FLAGS
03:15:59 4040 EXAMINE "folder1" (QRESYNC (1258000258 14))
[... Identical for all the folders ...]
03:15:59 4099 EXAMINE "folder90" (QRESYNC (1258000252 1))
03:15:59 4100 LIST "" "*"
03:15:59 4101 SELECT "INBOX"
03:15:59 4102 UID FETCH 1:* FLAGS
03:15:59 4103 LIST "" "*"
03:15:59 4104 EXAMINE "folder1"
[... Identical for all the folders ...]
03:15:59 4171 EXAMINE "folder90"
In the "good" gnus version, command 4100 onwards are missing,
transmission stops at command 4099.
Regards
next prev parent reply other threads:[~2011-02-23 2:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 11:31 Tassilo Horn
2011-02-07 11:44 ` Lars Ingebrigtsen
2011-02-07 11:55 ` Tassilo Horn
2011-02-07 11:59 ` Lars Ingebrigtsen
2011-02-07 12:17 ` Tassilo Horn
2011-02-07 12:21 ` Lars Ingebrigtsen
2011-02-07 12:39 ` Tassilo Horn
2011-02-07 12:57 ` Tassilo Horn
2011-02-14 3:35 ` Lars Ingebrigtsen
2011-02-14 9:21 ` Tassilo Horn
2011-02-15 21:28 ` Emilio Jesús Gallego Arias
2011-02-16 22:12 ` Lars Ingebrigtsen
2011-02-16 22:18 ` Emilio Jesús Gallego Arias
2011-02-16 22:24 ` Lars Ingebrigtsen
2011-02-17 0:27 ` Emilio Jesús Gallego Arias
2011-02-17 23:48 ` Lars Ingebrigtsen
2011-02-23 2:12 ` Emilio Jesús Gallego Arias
2011-02-23 2:18 ` Emilio Jesús Gallego Arias [this message]
2011-02-23 9:04 ` Lars Ingebrigtsen
2011-02-24 2:18 ` Emilio Jesús Gallego Arias
2011-02-25 3:33 ` Lars Ingebrigtsen
2011-02-19 9:45 ` Vincent Bernat
2011-02-20 1:22 ` Lars Ingebrigtsen
2011-02-20 13:14 ` Vincent Bernat
2011-02-07 21:21 ` Ludovic Courtès
2011-02-07 21:27 ` Michael Welsh Duggan
2011-02-14 3:35 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zkpnv6hl.fsf@babel.ls.fi.upm.es \
--to=egallego@babel.ls.fi.upm.es \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).