Gnus development mailing list
 help / color / mirror / Atom feed
From: larsi@ifi.uio.no (Lars Magne Ingebrigtsen)
Subject: Re: Articles spuriously marked as read?
Date: 19 Mar 1996 21:55:37 +0100	[thread overview]
Message-ID: <x668c0g9w6.fsf@eyesore.no> (raw)
In-Reply-To: David C Worenklein's message of Tue, 19 Mar 96 08:47:54 -0500

David C Worenklein <dcw@gcm.com> writes:

> This may be an nntp problem. Sometimes articles aren't properly
> propogated -- site x will get an article that you don't. Then user@x
> follows-up to the article, and the follow-up hits your site.

(I forgot to mention that the article(s) that I was *sure* I hadn't
seen really were in the group.)

It is definitely a Gnus bug.  I did the following yesterday:  1)
Process-marked two groups.  2)  `G s b' to brew SOUP packets.  

There were 5 unread articles in the second group, but only 2 of them
ended up being in the SOUP packet.  None of the other three articles
were cross-posted to the first group.

This might be a gnus-soup bug only.  (I certainly hope so.)  However,
when I try to repeat the bug, it just doesn't happen.  I'm starting to
leaning towards problems with nntp server communication when
requesting several articles rapidly, but that's highly speculative. 

-- 
  "Yes.  The journey through the human heart 
     would have to wait until some other time."


  reply	other threads:[~1996-03-19 20:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-03-19  1:24 Lars Magne Ingebrigtsen
1996-03-19 13:47 ` David C Worenklein
1996-03-19 20:55   ` Lars Magne Ingebrigtsen [this message]
1996-03-19 14:04 ` Jack Vinson
1996-03-19 17:31   ` Per Persson

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=x668c0g9w6.fsf@eyesore.no \
    --to=larsi@ifi.uio.no \
    /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).