From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/586 Path: news.gmane.org!not-for-mail From: those who know me have no need of my name Newsgroups: gmane.emacs.gnus.user Subject: Re: gnus/nnimap behaviour in case of failed fetch operations Date: 06 Jun 2002 00:16:16 GMT Organization: earthfriends Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1138667536 7538 80.91.229.2 (31 Jan 2006 00:32:16 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 00:32:16 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:27:49 2006 Original-Path: quimby.gnus.org!news.ccs.neu.edu!news.dfci.harvard.edu!news.cis.ohio-state.edu!usenet01.sei.cmu.edu!logbridge.uoregon.edu!newsfeed.stanford.edu!sn-xit-01!sn-post-01!supernews.com!news.supernews.com!not-for-mail Original-Newsgroups: gnu.emacs.gnus User-Agent: Gnus/5.090007 (Oort Gnus v0.07) XEmacs/21.4 (Informed Management (RC1), i686-redhat-linux) Original-X-Complaints-To: newsabuse@supernews.com Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:726 Original-Lines: 26 X-Gnus-Article-Number: 726 Tue Jan 17 17:27:49 2006 Xref: news.gmane.org gmane.emacs.gnus.user:586 Archived-At: in gnu.emacs.gnus i read: >those who know me have no need of my name >writes: >> in gnu.emacs.gnus i read: >>>Gnus marks non-existings articles as read. This goes back to >>>nntp, where it is not uncommon for the server to forget an article for >>>some reason or other. Gnus regards it as non-existing and moves on. >> >> and is unfortunately inappropriate behavior, sometimes. > >What would a better behaviour be? I can't really see anything else to >do. Retrieving the article didn't work, so the article doesn't exist. i'm not sure what would be better, in the context of gnus, but the article may yet appear. server farms often experience this sort of thing, and other newsreaders have made allowances for it (i.e., agent's `server creates articles out of order' setting); overview records can be available or article numbers consumed before the article itself is available. the same sort of behavior cannot (or at least should not) happen to imap servers, but the root of the problem is how gnus reacts not how nnimap reacts. -- bringing you boring signatures for 17 years