Gnus development mailing list
 help / color / mirror / Atom feed
From: Eze Ogwuma <zcaceog@ucl.ac.uk>
Cc: Eze Ogwuma <zcaceog@ucl.ac.uk>
Subject: Problem with Gnus and duplicate messages.
Date: Tue, 11 Feb 1997 10:00:38 +0000 (GMT)	[thread overview]
Message-ID: <Pine.A32.3.91.970211094614.97379B-100000@link-1.ts.bcc.ac.uk> (raw)

Hi,

Can anyone tell me what's going on. I am using Gnus to read my mail via
nnml. I also use nndoc to incorporate news spools from other machines and
I am testing nndir as a way to incorporate burst digests. 

When I get duplicate messages like announcements from "ding-announce" and
"ding" Gnus only displays one of them and no matter what I do I can't get
it to display them all. 

If I use "G f" to access a mail spool file copied to my machine all of the 
messages are not displayed.

Using "M P b" to mark and then "B r" to respool the messages only respools 
the messages displayed.

Yesterday I respooled a nndir file with over 6380 messages in it to a new 
nnml folder but Gnus only respooled about 5630.

Some of these messages were already on the system in other folders.

I don't mind not having to see duplicate messages, but I need Gnus to 
move and respool them just like they were visible.

I am using 5.4.11 (soon to be 5.4.12) with the default nnml settings for
duplicates. 

Can anyone help?

Thanks.
Eze Ogwuma.


             reply	other threads:[~1997-02-11 10:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-02-11 10:00 Eze Ogwuma [this message]
1997-02-11 12:54 ` Lars Magne Ingebrigtsen
1997-02-11 22:21   ` Eze Ogwuma
1997-02-12  8:51     ` Lars Magne Ingebrigtsen
1997-02-13  1:11       ` Eze Ogwuma
1997-02-14  9:31         ` Lars Magne Ingebrigtsen
1997-02-14 15:23           ` Eze Ogwuma

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=Pine.A32.3.91.970211094614.97379B-100000@link-1.ts.bcc.ac.uk \
    --to=zcaceog@ucl.ac.uk \
    /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).