[prev in list] [next in list] [prev in thread] [next in thread] 

List:       spamassassin-devel
Subject:    [Bug 5258] meta SOMERULE (/__SOMERULE_/) > 5
From:       bugzilla-daemon () issues ! apache ! org
Date:       2007-03-26 11:06:34
Message-ID: 5258.4607A93A.B30E4CC0.dev () spamassassin ! apache ! org
[Download RAW message or body]

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5258


quarl.sabugz@quarl.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|meta SOMERULE (__SOMERULE_* |meta SOMERULE
                   |> 5)                        |(/__SOMERULE_/) > 5




------- Additional Comments From quarl.sabugz@quarl.org  2007-03-26 04:06 -------
Since SpamAssassin is all about regexps, I decided to implement it using
regexpes rather than globbing, for more expressiveness.

I'm proposing the patch attached as meta_regexp.patch, which allows the following:

body AA_1 /aa/
body AA_2 /bb/
meta AA_MULTI_2 (/AA_[0-9]+/) >= 2
meta AA_MULTI_3 (/AA_[0-9]+/) >= 3
body AA_3 /cc/
body AA_4 /dd/

Notes:
- Regular expressions have to be enclosed in (/.../), including the parentheses.
 This makes it easy to lex, otherwise arithmetic operators might confuse things.
- Flags would have to be specified like (/(?i).../) instead of (/.../i), though
I don't see any regexp flags being useful at the moment.
- Regexp expansion is done at check time, so that more rules can be added after
the meta test is defined.
- Meta rules without (/.../) are unaffected, and this used to be
undefined/illegal behavior

Regards, Karl




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[prev in list] [next in list] [prev in thread] [next in thread]