Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: nnimap fails to fetch some articles
Date: Mon, 07 Mar 2005 22:45:48 +0100	[thread overview]
Message-ID: <ilubr9vi0z7.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3eker2tk7.fsf@pacbell.net> (Bjorn Solberg's message of "Mon, 07 Mar 2005 10:35:04 -0800")

Bjorn Solberg <bjorn_ding@hekneby.org> writes:

> Simon Josefsson writes:
>
>> Bjorn Solberg <bjorn_ding@hekneby.org> writes:
>>> When I do 5 RET to fetch the last 5 messages, I consistently only get 3,
>>> missing some in-between: It's getting N-3, N-1 and N, skipping N-4 and
>>> N-2.
>>> 
>>> If I fetch the last 6 messages, it skips N-5 in addition.
>>> 
>>> If I fetch the last 7 messages, it skips the same as for 6 but fetches
>>> message# N-6.
>>> 
>>> The full *imap-log* is 800 lines long for the 5 RET, see below for the
>>> last 400+ lines.  It looks like it's issuing the correct command, "UID
>>> FETCH 780:784 [...]" but for some reason it doesn't display the first and
>>> third of those last 5 messages.
>
>> I didn't spot any problem in the IMAP log.
>
>> After you have entered the group with 5 RET, what is in the " *nntpd*"
>> buffer?  Note leading SPC.
>
>> One idea is that the IMAP parser doesn't understand the responses and
>> skip the article, in that case the *nntpd* buffer would only contain
>> the information from three of the articles.
>
> " *nntpd*" shows an entry for all 5 messages.  I have received new
> messages since last, so now it show only 2 messages when I do 5 RET.
> Which means this is somehow content-related.
>
> However, I see a pattern in " *nntpd*" now: " *nntpd*" shows that the
> messages aren't sorted by id.  For example, doing 5 RET I see entries 793
> 795 794 792 791 in " *nntpd*", and only 793 and 795 is shown in the
> Summary buffer.

Ah, thanks, that is it.  The IMAP server returned the articles out of
order.  Which I think is perfectly legal.  Maybe the following patch
help?  Untested.

--- nnimap.el	04 Mar 2005 17:59:01 +0100	7.17
+++ nnimap.el	07 Mar 2005 22:45:30 +0100	
@@ -710,6 +710,8 @@
 			    (if (imap-capability 'IMAP4rev1)
 				(format "BODY.PEEK[HEADER.FIELDS %s])" headers)
 			      (format "RFC822.HEADER.LINES %s)" headers)))))
+      (with-current-buffer nntp-server-buffer
+	(sort-lines))
       (and (numberp nnmail-large-newsgroup)
 	   (> nnimap-length nnmail-large-newsgroup)
 	   (nnheader-message 6 "nnimap: Retrieving headers...done")))))



  reply	other threads:[~2005-03-07 21:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-05  0:47 Bjorn Solberg
2005-03-05 11:00 ` Simon Josefsson
2005-03-07 18:35   ` Bjorn Solberg
2005-03-07 21:45     ` Simon Josefsson [this message]
2005-03-07 22:00       ` Bjorn Solberg
2005-03-07 22:40       ` Bjorn Solberg
2005-03-08  0:40         ` Simon Josefsson
2005-03-08 19:44           ` Reiner Steib
2005-03-08 21:32             ` Simon Josefsson
2005-03-09 14:11               ` David S. Goldberg
2005-03-09 17:43                 ` Ted Stern
2005-03-10 15:56                   ` David S. Goldberg
2005-03-09 18:14                 ` Bjorn Solberg
2005-03-09 19:52                   ` David S. Goldberg
2005-03-08 22:42           ` Arne Jørgensen
2005-03-10  9:22             ` Simon Josefsson

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=ilubr9vi0z7.fsf@latte.josefsson.org \
    --to=jas@extundo.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).