From: Ted Zlatanov <tzz@lifelogs.com>
Cc: Ding Mailing List <ding@gnus.org>
Subject: Re: nnmail-split-fancy?
Date: Fri, 25 Jul 2003 16:29:09 -0400 [thread overview]
Message-ID: <4n65lq5p0q.fsf@chubby.bwh.harvard.edu> (raw)
In-Reply-To: <ywku8yqmftxt.fsf@snowblower.colorado.edu> (savoie@nsidc.org's message of "Fri, 25 Jul 2003 10:32:46 -0600")
The following message is a courtesy copy of an article
that has been posted to gnu.emacs.gnus as well.
On Fri, 25 Jul 2003, savoie@nsidc.org wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> On Thu, 24 Jul 2003, savoie@no-spam.nsidc.org wrote:
>>> What I'm really looking for is the function that will let me say
>>> (: junk-this "regexp") in my nnmail-split-fancy, but maybe I
>>> should look into spam.el and see what it can do for me.
>>
>> Right now spam.el won't help, but I could add a spam-use-regex-body
>> function similar to spam-use-regex-headers. The
>> spam-use-regex-body function could return an arbitrary group name,
>> unlike spam-use-regex-headers (only spam-use-ifile can return an
>> arbitrary group right now so this is somewhat unusual, but not a
>> problem).
>
> That looks like pretty much exactly what I'm trying to do. I can
> then customize the spam-regex-body-spam variable to have all of the
> expressions I want to filter on? I think I get it.
>
> That would be cool if you would.
I added a binary check spam-use-regex-body (nil by default) that you
can customize through spam-regex-body-spam and spam-regex-body-ham
(empty lists by default). If you set spam-user-regex-body to t and
use spam-split in your split-fancy rules, you should be all set. It's
exactly like spam-use-regex-headers except that a) it searches the
whole body, b) prints slightly different messages, c) uses
spam-regex-body-spam and spam-regex-body-ham instead of
spam-regex-headers-spam and spam-regex-headers-ham.
If you need the ability to have multiple group names that will take a
bit longer. Test this and let me know how it works, if there are
bugs... It's in CVS.
Ted
parent reply other threads:[~2003-07-25 20:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <ywku8yqmftxt.fsf@snowblower.colorado.edu>]
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=4n65lq5p0q.fsf@chubby.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--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).