Gnus development mailing list
 help / color / mirror / Atom feed
From: Eze Ogwuma <zcaceog@ucl.ac.uk>
Cc: ding@ifi.uio.no
Subject: Re: Problem with Gnus and duplicate messages.
Date: 13 Feb 1997 01:11:27 +0000	[thread overview]
Message-ID: <m3ohdpse68.fsf@ucl.ac.uk> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 12 Feb 1997 09:51:47 +0100

Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:

> Eze Ogwuma <zcaceog@ucl.ac.uk> writes:
> 
> > > > 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. 
> > > 
> > > That's odd.  What's your `nnmail-treat-duplicates' variable?
> > 
> > warn
> 
> So's mine, but I haven't had Gnus misbehave at all in this area for a
> long time.  You do do (be do do) your mail splitting with Gnus?

Yes, I use Gnus to split my mail when I get it home.

The problem is this:

I copy the file from /usr/spool/mail/ to my home directory and take it
home.

At home I use nndoc to open the file, "M P b" to mark the messages and
"B r" to re-spool with nnml as the backend.

Not all the messages are re-spooled.

I have just started to use SOUP. What I am doing is to read the file
from /usr/spool/mail with nndoc.

When I use "G s b" to brew soup not all the articles are taken. The
duplicates are left.


> > > Only one copy of messages with the same Message-ID will be displayed. 
> > 
> > But when I re-spool only one copy is re-spooled and I can never see both 
> > copies.
> 
> Yes.

I have had to re-spool mail groups to do change the way messages are
filed and also to "pack" groups. As Gnus doesn't show all the messages
in a group, how can I select them all so that they can be re-spooled?

I have had cases where Gnus has re-spooled a incomplete file from an
exmh folder and left the complete version of this message behind. It
then refused to "see" or move this message. I only knew it was there
because I used exmh to check.

If Gnus will not "see" duplicate messages then surely everyone who
moves or re-spools messages is loosing mail.

-- 
Eze Ogwuma


  reply	other threads:[~1997-02-13  1:11 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 [this message]
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=m3ohdpse68.fsf@ucl.ac.uk \
    --to=zcaceog@ucl.ac.uk \
    --cc=ding@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).