> I don't want to spend many time making the patch, unless it goes immediately
> into CVS, as keeping it sync with CVS for weeks/months is a nightmare...
> If I have to do the fork&sync way, i'll fork everything and redesign ruleset
> syntax to better fit my needs for the C version...
Rules tend
Hi,
> On Thu, 2002-02-21 at 13:42, Arpi wrote:
> > when will it be implemented, or better: when will you accept such patch fo
> r
> > ruleset? (i cannot modify the perl code, as i don't know the perl languege
> > nor the spamassassin core enough, but i could help making this optimzation
> > to th
Ok, so this thread got my to go read through man perlre in a little more
detail. I've found the following as a result:
PerMsgStatus.pm uses $& and $', which apparently will cause *all* regex
matching to be much slower program wide. I'll try to rewrite the one
line on which that occurs; we shoul
Heh, yeah. My syntax would make it seem that it would allow that. And
I agree that allowing that would be better. But allowing that would
mean more coding ;) I'll probably do it anyway...
C
On Thu, 2002-02-21 at 14:20, Arpi wrote:
> Hi,
>
> > On 21 February 2002, Craig Hughes said:
> > > I
On Thu, 2002-02-21 at 13:42, Arpi wrote:
> when will it be implemented, or better: when will you accept such patch for
> ruleset? (i cannot modify the perl code, as i don't know the perl languege
> nor the spamassassin core enough, but i could help making this optimzation
> to the ruleset)
You ca
On 21 February 2002, Arpi said:
> anyway, i have a request:
> could you add a new rule type, for plain text matches?
> searching for a text string is always simpler and faster than for regexps,
> and many of your regexps are such strings (/some words/i) and there will be
> much more when start add
Hi,
> On 21 February 2002, Craig Hughes said:
> > I had been thinking about creating a "multiple-rule" format for rules,
> > where in order to match a rule, you would have to match a sequence of
> > regexes, eg:
> >
> > rawbody ASCII_FORM_ENTRY /_{30,}/
> > and rawbody ASCII_FORM_ENTRY /[
Hi,
> I had been thinking about creating a "multiple-rule" format for rules,
> where in order to match a rule, you would have to match a sequence of
> regexes, eg:
>
> rawbody ASCII_FORM_ENTRY /_{30,}/
> and rawbody ASCII_FORM_ENTRY /[^<][A-Za-z][A-Za-z]+.{1,15}?\s+_{30,}/
>
> the "and"
