From: Harry Putnam <reader@newsguy.com>
Subject: Re: Controlling Destination of Respooled Messages
Date: 11 Jun 1998 15:19:32 -0700 [thread overview]
Message-ID: <m3wwanint7.fsf@newsguy.com> (raw)
In-Reply-To: dave-mlist@bfnet.com's message of "11 Jun 1998 12:23:01 -0700"
dave-mlist@bfnet.com writes:
> When I use `B r' to respool mail articles, I can't control the fact
> that they go into "nnml+mail.misc". But I want to set this to be any
> number of archive groups. Is it possible?
Yes, you can even set up whole alternate split rules for respooling just
about anywhere you want and just keep in commented out in .gnus till you
need it.
I think you need to read the 'splitting' pages. From group/summary
buffer C-c C-i to get Gnus info then 'g' (goto node) 'splitting'<RET>
(no quotes) will get you there.
Then experiment with some of the splitting examples there.
--
Harry Putnam reader@newsguy.com
next prev parent reply other threads:[~1998-06-11 22:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-11 19:23 dave-mlist
1998-06-11 22:19 ` Harry Putnam [this message]
1998-06-12 11:54 ` Kai Grossjohann
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=m3wwanint7.fsf@newsguy.com \
--to=reader@newsguy.com \
/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).