From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Problem with Gnus and duplicate messages.
Date: 14 Feb 1997 10:31:19 +0100 [thread overview]
Message-ID: <m2pvy368ew.fsf@proletcult.slip.ifi.uio.no> (raw)
In-Reply-To: Eze Ogwuma's message of 13 Feb 1997 01:11:27 +0000
Eze Ogwuma <zcaceog@ucl.ac.uk> writes:
> When I use "G s b" to brew soup not all the articles are taken. The
> duplicates are left.
Yes, that's natural. nndoc doesn't do any Message-ID accouning, so if
there are several messages with the same Message-ID, only the first
will be displayed.
> If Gnus will not "see" duplicate messages then surely everyone who
> moves or re-spools messages is loosing mail.
Well, perhaps nndoc should take more care. I've now added this to the
todo list.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
next prev parent reply other threads:[~1997-02-14 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-02-11 10:00 Eze Ogwuma
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 [this message]
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=m2pvy368ew.fsf@proletcult.slip.ifi.uio.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).