From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: "fall through" spam filtering with Sieve?
Date: Thu, 14 Feb 2002 12:26:10 +0100 [thread overview]
Message-ID: <iluy9hwwbhp.fsf@extundo.com> (raw)
In-Reply-To: <87vgd08ovy.fsf@home.lan> (Steinar Bang's message of "Thu, 14 Feb 2002 09:10:41 +0100")
Steinar Bang <sb@dod.no> writes:
>>>>>> Simon Josefsson <jas@extundo.com>:
>
>> Yes. Add Sieve rules for all your groups (manually using G p from
>> group buffer, or M-x gnus-sieve-article-add-rule RET for some
>> heuristics that work for mailing lists in the summary/article
>> buffer), create the .sieve file using D g from the group buffer and
>> upload it to your server using C-c RET and C-c l in the .sieve
>> buffer.
>
> Yes. This lets me add rules for nnimap groups, saying that everything
> that fits a particular rule should go into that group. I already knew
> that...:-)
>
> What I'm wondering is if it is possible to associate a rule with an
> nnimap group saying basically "everything not matched by any other
> rule should go into this group"? Or maybe if there is some way of
> ordering the rules for the different groups?
Aha. Maybe you could add something like this after the "## End Gnus
Sieve Script" marker:
fileinto "INBOX.spam";
>> There are some example Sieve rules in the Sieve manual as well.
>
> Hmm... yes... but they don't seem to cover this case either...? Or is
> there something I'm missing?
I guess I was thinking of adding a always-matching rule on your spam
group
if header :contains "Received" "" {
fileinto "INBOX.spam";
}
and making sure it was last in the file (which unfortunately isn't
possible right now, I think).
next prev parent reply other threads:[~2002-02-14 11:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 22:01 Steinar Bang
2002-02-13 23:06 ` Simon Josefsson
2002-02-14 8:10 ` Steinar Bang
2002-02-14 9:12 ` Kai Großjohann
2002-02-14 11:26 ` Simon Josefsson [this message]
2002-02-14 13:04 ` Steinar Bang
2002-02-14 13:19 ` 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=iluy9hwwbhp.fsf@extundo.com \
--to=jas@extundo.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).