Actually,  This is my RegEx and nothing "oficially" went wrong.  The address is so long that the SpamFilter RegEx Parser reached a hard coded limit and the error you get is as you see.  This is a non critical error that Roberto can explain MUCH better than I can but it does not cause any issues.  The SpamFilter just goes on to the next filter from there.

This RegEx, in my system, catches a bunch and barfs on a bunch like you have seen but it still does reduce the spam so I have learned to ignore those errors.

Dan S.

Ronny T,

Dan is absolutely correct in his statement. Some RegEx expressions require a string to be parsed several times with recursive loops in order to match all searches. If the "recursivity" functions are very "deep", meaning a recursive function calls itself, which then calls itself, and calls itself again, and again etc, this could cause some Windows stack overflows and bring the server to its knees (especially if several incoming emails are processed concurrently). In order to avoid this, we've placed a hardcoded limit in how many levels deep a recursive function can go. When the limit is reached a "soft error" breaks the loop and halts the search for that particular string. This is totally harmless, and will not cause any other errors, but will usually cause the particular searh string to be ignored.

Roberto F.
LogSat Software