Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <simon@josefsson.org>
Cc: ding@gnus.org
Subject: Re: nnml -> nnimap (preserving Xrefs)
Date: 30 Aug 2000 10:45:54 +0200	[thread overview]
Message-ID: <ilu7l8zi1bx.fsf@barbar.josefsson.org.d.dynas.se> (raw)
In-Reply-To: <52em3770ov.fsf@sean.ebone.net>

Sean Doran <smd@ebone.net> writes:

>    First problem: it took a bit to realize I needed the
>                   "my-imap-splitter" function to avoid
>                   EVERYTHING being crossposted into "misc"
>                   (instead of just new mail being moved there)
>                   I (naively) did "mv misc INBOX" + M-g
>                   and now there are *lots* of duplicates
>                   in each group.   How do I get rid of them?

I don't think there's any built-in functionality for doing that.  You
could write a function that iterate over `gnus-newsgroup-headers',
comparing msgid's and process marking some of them.

Perhaps it would be useful to include it in Gnus -- i.e. "Process Mark
all Duplicate Articles".

>    Second problem: How does anything know that the
>                    the nnimap-split-rule crossposted an
>                    article?  That is, how do I get marks
>                    to propagate to all the groups an
>                    nnimap article is crossposted into?

It doesn't.  IMAP doesn't support the concept of cross-posting.  Right
now, the article is simply copied into all mailboxes.  And until more
servers support the ANNOTATE draft, there's no way we can attach any
(such as a Xref header) information on the article.




  reply	other threads:[~2000-08-30  8:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-30  5:55 Sean Doran
2000-08-30  8:45 ` Simon Josefsson [this message]
2000-09-01 10:36   ` Steinar Bang
2000-09-01 10:58     ` 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=ilu7l8zi1bx.fsf@barbar.josefsson.org.d.dynas.se \
    --to=simon@josefsson.org \
    --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).