The regular expression engine in Pegasus Mail and Mercury considerably pre-dates almost all of the Linux implementations, which means that it has legacy issues (i.e, it is so widely-used that I can't easily change it without invalidating many, many sites' data).
I *did* expand the regex format a few years back, to include various whitespace metacharacters (/w and /W in particular), but things like "start of line" and "end of line" aren't directly supported because the engine makes them explicit (as a general rule, all matches inherently start at the beginning of a line and end at the end of a line).
Moving to a different regex format would not be a trivial task - it would require fundamental changes in the way many features in Pegasus Mail and Mercury operate, and would invalidate every current expression stored by any Pegasus Mail or Mercury user.
You are welcome to suggest extensions to the existing regex engine, though - I will consider any reasonable request if it is feasible and can be done without creating significant backwards-compatibility problems.
Cheers!
-- David --
<p>The regular expression engine in Pegasus Mail and Mercury considerably pre-dates almost all of the Linux implementations, which means that it has legacy issues (i.e, it is so widely-used that I can't easily change it without invalidating many, many sites' data).
I *did* expand the regex format a few years back, to include various whitespace metacharacters (/w and /W in particular), but things like "start of line" and "end of line" aren't directly supported because the engine makes them explicit (as a general rule, all matches inherently start at the beginning of a line and end at the end of a line).
Moving to a different regex format would not be a trivial task - it would require fundamental changes in the way many features in Pegasus Mail and Mercury operate, and would invalidate every current expression stored by any Pegasus Mail or Mercury user.
You are welcome to suggest extensions to the existing regex engine, though - I will consider any reasonable request if it is feasible and can be done without creating significant backwards-compatibility problems.
Cheers!
-- David --
</p>