> [EMAIL PROTECTED] wrote:
>
>>Here's an exception I've been receiving a few times in debug.log over
>>the past couple days (see below). I haven't made any TMDA changes in at
>>least a couple weeks, but this has just started showing up yesterday.
>>
>>Does anyone know what could be causing this, and how I can fix it?
>>
>>
> I got it several times when I had a regexp which contained the term
> "(.*\n)*" -- if it didn't find a quick match to the rest of the
> expression, that term could encompass the remainder of the e-mail.
> Large e-mails which didn't match the pattern caused that exception,
> because there were too many backtracking points to check. The solution
> was to set a maximum number of repetitions: "(.*\n){,5}" Check if you
> have anything in your regexp which could theoretically scale to all or
> most of the e-mail.....
Well, I checked my rules, and I indeed had one similar to what you
mentioned above ... and it could easily have gobbled up an entire
message. I made the change you suggested, and I hope that my problem
has now ended.
So thank you very much.
And this brings up another question:
Consider the following regex fragment within a TMDA rule:
[^<>@]*
My intention is for it to match the longest string within a single line
that does not contain the characters '<', '>', or '@'. But will this
pattern match a newline or not? If I don't want it to match a newline,
do I have to render it as follows?
[^<>@\n]*
Thanks.
--
Lloyd Zusman
[EMAIL PROTECTED]
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
