From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: How to combine spam-split with Subject filtering.
Date: Tue, 08 Feb 2005 14:24:25 -0500 [thread overview]
Message-ID: <4nhdkmvora.fsf@lifelogs.com> (raw)
In-Reply-To: <86zmzeqwcs.fsf@mat.ucm.es>
On Wed, 12 Jan 2005, oub@mat.ucm.es wrote:
> Finally I got my BBDB and spam-stat based spam filtering to work for
> my imap server. Now my university provides finally its own spam
> filter, which add to possible spam at the beginning of the Subject the
> phrase:
> [SPAM POSIBLE:]
>
> So I would like to take care of this in the splitting process, and
> split every mail with this subject into a different imap folder so I
> thought the following setting should work:
> (setq
> nnimap-split-rule 'nnimap-split-fancy
> nnimap-split-inbox "INBOX"
> nnimap-split-fancy
> '(|
> ("Subject" "[POSIBLE SPAM]:" "SPAM.POSS")
> (: setq spam-use-BBDB-exclusive nil)
> (: spam-split 'spam-use-BBDB 'spam-use-stat "SPAM.REAL")
> (: setq spam-use-BBDB-exclusive t fake-variable nil)
> (: spam-split 'spam-use-BBDB "SPAM.HAM")
> (: setq spam-use-BBDB-exclusive nil)
> "MAILBOX"))
>
> it did not however. What do I miss.
You could use spam-use-regex-headers. Add an entry to the
spam-regex-headers-spam list to match your subject. The check will be
done against the headers as a whole using re-search-forward so just
escape the brackets appropriately.
It would be nice if in addition to "Subject" we had "Subject+raw" as
an alternative in case the user wants an exact match without regular
expressions (ditto for all the other special headers that can be used,
e.g. "From+raw"). Then "[POSSIBLE SPAM]" would just match, without
the confusion about regex escaping and word boundaries.
Ted
next prev parent reply other threads:[~2005-02-08 19:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86zmzeqwcs.fsf@mat.ucm.es>
[not found] ` <m2r7kqggr7.fsf@Stella-Blue.local>
[not found] ` <v97jmhhhcg.fsf@marauder.physik.uni-ulm.de>
[not found] ` <864qhlr4n0.fsf@mat.ucm.es>
[not found] ` <866521cyr5.fsf@mat.ucm.es>
[not found] ` <16870.34083.953155.509283@parhasard.net>
2005-01-13 15:04 ` Uwe Brauer
2005-02-08 19:24 ` Ted Zlatanov [this message]
2005-02-10 18:16 ` Uwe Brauer
2005-02-10 18:15 ` Ted Zlatanov
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=4nhdkmvora.fsf@lifelogs.com \
--to=tzz@lifelogs.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).