From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/1766 Path: news.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.gnus.user Subject: Re: pseudo-article ? Date: Sun, 05 Jan 2003 02:38:59 +0100 Message-ID: References: <87it1f6ob0.fsf@bretagne.rail.eu.org> <87ofb0vgw6.fsf@bretagne.rail.eu.org> <87hedd2g9h.fsf@kuntu.zangpo.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1138668446 12641 80.91.229.2 (31 Jan 2006 00:47:26 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 00:47:26 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:29:40 2006 Original-Path: quimby.gnus.org!not-for-mail Original-Newsgroups: gnu.emacs.gnus Original-NNTP-Posting-Host: 178.230.13.217.in-addr.dgcsystems.net Original-X-Trace: quimby.gnus.org 1041730889 16224 217.13.230.178 (5 Jan 2003 01:41:29 GMT) Original-X-Complaints-To: usenet@quimby.gnus.org Original-NNTP-Posting-Date: 5 Jan 2003 01:41:29 GMT User-Agent: Gnus/5.090008 (Oort Gnus v0.08) XEmacs/21.4 (Native Windows TTY Support, i686-pc-linux) Cancel-Lock: sha1:HipL+FQ7zRyC+7ZlUk6Q5BBylUc= Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:1906 Original-Lines: 39 X-Gnus-Article-Number: 1906 Tue Jan 17 17:29:40 2006 Xref: news.gmane.org gmane.emacs.gnus.user:1766 Archived-At: Martin Schmitz writes: > Erwan David writes: > >> Nevin Kapur writes: >> >>> It's not an error with a trace, just a message in the minibuffer. >>> Here's an excerpt from my " *Message-Log*", when I try to fetch the >>> parent of your posting: >>> >>> Couldn't find parent >>> Couldn't go to article 63235 >>> Can't find article 63235 <- hitting '^' again. >>> Generating summary...done >>> Generating summary... >>> This is a pseudo-article <--- after hitting '^' >>> Generating summary...done >>> Generating summary... >>> >>> Indeed, if I type `j' followed by 63235, I get the same message. >>> Instead, if I enter the group with say 10 RET, so that the parent >>> (63235) is visible then both `j' and '^' work as expected. >>> >>> This behavior is repeatable for a few articles. Other articles can be >>> 'j'umped to without problems. >> >> That's exactly the behaviour I see. > > The same here for a long time now and still getting worse. But it only > appears in IMAP-Mailboxes. I ask myself if it could be uw-imapd's fault...? Try setting `imap-log' and send the output from *imap-log* after doing this. > Respooling and anything else does not work... Is there any solution > known to this now? No. Move the article you want to respool to the nnimap-split-inbox and mark it unread and press g in the group buffer.