From: Arnd Kohrs <kohrs@acm.org>
Subject: Conversation Splitting (Was: fetching mail for multiple servers)
Date: 21 Jun 2000 15:27:24 +0200 [thread overview]
Message-ID: <xljwvjjp3k3.fsf_-_@abyss.eurecom.fr> (raw)
In-Reply-To: Harry Putnam's message of "20 Jun 2000 06:23:19 -0700"
>>>>> "Harry" == Harry Putnam <reader@newsguy.com> writes:
Harry> Coming to think of it, it might be necessary to also allow
Harry> nnmail-split-fancy as server parameter, too.
I use ¨conversation splitting¨ in combination with group splitting with
the following settings:
(setq nnmail-crosspost nil)
(setq nnmail-split-methods 'gnus-group-split)
(setq gnus-group-split-default-catch-all-group
'(| (: nnmail-split-fancy-with-parent)
"mail.misc"))
Of course, no other group should be configured with 'catch-all' !
First, messages are split into mailing lists, then into conversations
and if that didn't work they end up in my default box.
Other fancy splits may be defined in this default rule. IMO, it
shouldn't be hard to write a function that rewrites old-style splitting
rules into fancy splits - on the other hand it is also not hard to do it
manually:
;; old style
((r1 g1)
......
(rn gn)
default)
becomes
;; fancy
(| (any r1 g1)
..........
(any rn gn)
default)
(The seemingly complex nature of fancy-splits scared me a long time away
from converting to fancy splitting)
Arnd
--
The Active WebMuseum: Your personalized access to art paintings.
Visit now -> http://www.eurecom.fr/~kohrs/museum.html
next prev parent reply other threads:[~2000-06-21 13:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-20 9:36 fetching mail for multiple servers Kai Großjohann
2000-06-20 10:24 ` Harry Putnam
2000-06-20 12:12 ` Kai Großjohann
2000-06-20 13:23 ` Harry Putnam
2000-06-20 16:35 ` Kai Großjohann
2000-06-21 13:27 ` Arnd Kohrs [this message]
2000-06-20 13:55 ` Bjørn Mork
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=xljwvjjp3k3.fsf_-_@abyss.eurecom.fr \
--to=kohrs@acm.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).