From: James Cloos <cloos@jhcloos.com>
To: ding@gnus.org
Subject: An example of an nnimap group where the Group count is always wrong
Date: Fri, 08 Apr 2011 18:14:54 -0400 [thread overview]
Message-ID: <m3pqow5r0p.fsf@jhcloos.com> (raw)
I noticed this with one of my nnimap groups which always gets wrong info
in Group.
Everytime I run g or M-g this group shows seven unread articles in its
Group count, but selecting it always says zero unread articles.
As you can see, even though SELECT shows zero exist and zero recent, and
even though UID FETCH 1:* FLAGS shows no articles, gnus is convinced that
uids 29 through 35 exist.
This is from repeated M-g and SPACE:
read(0, "103351 SELECT \"dsnp-interest@complang.org\"\r\n"
write(5, "* 0 EXISTS\r\n"
write(5, "* 0 RECENT\r\n"
write(5, "* FLAGS (\\Seen \\Answered \\Deleted \\Flagged \\Draft)\r\n"
write(5, "* OK [PERMANENTFLAGS (\\Seen \\Answered \\Deleted \\Flagged \\Draft)]\r\n"
write(5, "* OK [UIDNEXT 0] Predicted next UID\r\n"
write(5, "* OK [UIDVALIDITY 41557] UID value\r\n"
write(5, "103351 OK [READ-WRITE] SELECT completed\r\n"
read(0, "103352 UID FETCH 1:* FLAGS\r\n"
write(5, "103352 OK UID FETCH completed\r\n"
read(0, "103353 UID FETCH 29:35 (UID RFC822.SIZE BODYSTRUCTURE BODY.PEEK[HEADER.FIELDS (Subject From Date Message-Id References In-Reply-To Xref To Newsgroups)])\r\n"
write(5, "103353 OK UID FETCH completed\r\n"
read(0, "103354 SELECT \"dsnp-interest@complang.org\"\r\n"
write(5, "* 0 EXISTS\r\n"
write(5, "* 0 RECENT\r\n"
write(5, "* FLAGS (\\Seen \\Answered \\Deleted \\Flagged \\Draft)\r\n"
write(5, "* OK [PERMANENTFLAGS (\\Seen \\Answered \\Deleted \\Flagged \\Draft)]\r\n"
write(5, "* OK [UIDNEXT 0] Predicted next UID\r\n"
write(5, "* OK [UIDVALIDITY 41557] UID value\r\n"
write(5, "103354 OK [READ-WRITE] SELECT completed\r\n"
read(0, "103355 UID FETCH 1:* FLAGS\r\n"
write(5, "103355 OK UID FETCH completed\r\n"
read(0, "103356 UID FETCH 29:35 (UID RFC822.SIZE BODYSTRUCTURE BODY.PEEK[HEADER.FIELDS (Subject From Date Message-Id References In-Reply-To Xref To Newsgroups)])\r\n"
write(5, "103356 OK UID FETCH completed\r\n"
The info in .newsrc.eld for that group is:
("nnimap+l:dsnp-interest@complang.org" (55 . 24) nil
((seen (7 . 35)) (cache 34)) "nnimap:l"
((modseq) (uidvalidity . "41557") (active 29 . 35) (permanent-flags %Seen %Answered %Deleted %Flagged %Draft) (timestamp 19864 55661) (imap-status . "0 1 0")))
Art 34 does exist in ~/News/cache as claimed in newsrc. And is the only
art there.
The Group buffer has been broken ever since the support for syncing to
the imap server was added. Immediately before that it worked perfectly.
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next reply other threads:[~2011-04-08 22:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 22:14 James Cloos [this message]
2011-04-08 23:27 ` [CORRECTED] " James Cloos
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=m3pqow5r0p.fsf@jhcloos.com \
--to=cloos@jhcloos.com \
--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).