Tim Legant <[EMAIL PROTECTED]> writes: > Lloyd Zusman <[EMAIL PROTECTED]> writes: > >> Lloyd Zusman <[EMAIL PROTECTED]> writes: >> >> >> Lloyd Zusman <[EMAIL PROTECTED]> writes: >> >> >> >>> File "./TMDA/FilterParser.py", line 1069, in firstmatch >> >>> File "/usr/local/lib/python2.3/sre.py", line 137, in search >> >>> return _compile(pattern, flags).search(string) >> >>> RuntimeError: maximum recursion limit exceeded >> >> >> >> Something in your configuration has exceeded the maximum depth of the >> >> Python interpreter stack. This limit prevents infinite recursion from >> >> causing an overflow of the C stack and crashing Python. >> >> >> >> Check your 'body' and/or 'headers' rules. You probably bungled one of >> >> the regular expressions. >> > >> > I'll check, but I haven't changed any of those rules in months. Could >> > there be something about certain incoming messages which triggers this >> > kind of error only under certain cases? >> >> I didn't change any regexp rules, but I did add the >> "[EMAIL PROTECTED]" lines (below) to my whitelist recently (the >> non-"bounces" lines were there from before). Could this combination of >> entries be triggering the error, perhaps? > > No, it's definitely one of the 'body' or 'headers' rules that is > causing the problem. Perhaps the Python 2.3 implementation of regular > expressions tightened up something it previously allowed. If you're > not comfortable posting the rules you use, you can send them to me and > I'll try to determine which one it is.
I'll send the rules a little later today (I'm at work and they aren't readily accessible). In the mean time, you should know that most emails pass through these rules with no problem. These rules are the first step within my incoming filter, and they therefore are applied to each and every piece of incoming email. The only emails which cause this exception have been a small subste of those that come from this mailing list, and that only started 2-3 days ago. I haven't upgraded anything on my machine for at least a week before that. That's why I thought that my new whitelist "tmda-*-bounces" rules might have been the culprit, since I added them around the time that this started happening, and because only tmda mailing list messages have triggered the exception. Also ... if the error is in the format of the regex of one or more of these rules, how could it be that 99 percent of the emails to which the rules are applied do not trigger the exception? At any rate, I'll send you the rules later today. And thanks! -- Lloyd Zusman [EMAIL PROTECTED] _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
