From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@hpc.uh.edu
Subject: Re: Tricky (to me) mail splitting
Date: Wed, 05 Dec 2001 09:53:09 +0100 [thread overview]
Message-ID: <vafg06q59qi.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <87zo4ypzd7.fsf@pooh.int> (Kirk Strauser's message of "04 Dec 2001 13:19:16 -0600")
Kirk Strauser <kirk@strauser.com> writes:
> (setq
> nnmail-split-methods 'bbdb/gnus-split-method
> bbdb/gnus-split-nomatch-function 'gnus-group-split
> )
>
> Given that setup (taken pretty much straight from the BBDB manual), where
> would I insert the rule you gave?
Well, there is a very good reason why I didn't answer this question
in my last message: I don't know the answer :-)
I'm sorry about this.
I'm not sure whether nnmail-split-fancy supports the "\\1" feature.
If it does, then things would be simple.
kai
--
Simplification good! Oversimplification bad! (Larry Wall)
prev parent reply other threads:[~2001-12-05 8:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 16:20 Kirk Strauser
2001-12-04 17:31 ` Kai Großjohann
2001-12-04 19:19 ` Kirk Strauser
2001-12-05 8:53 ` Kai Großjohann [this message]
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=vafg06q59qi.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@hpc.uh.edu \
/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).