>>>>> "TN" == Tom Neff <email@example.com> writes:
TN> Frankly I think that the best of all worlds would be to add something
But you're already amazingly close to what's already there! For efficiency
and all around better code the access check routines don't get the entire
message; instead the taboo matches are saved and the severities are passed
into the access routines along with variables containing the state of all
of the other transgressions. And you do have a simple language that lets
you do the logical connectives and such.
TN> Unfortunately there are security issues here that would make taboo_eval
TN> useful only for "friendly" sites.
My scheme does not have that problem because the language is "compiled"
into perl instead of being perl itself, and I have taken rather strict
security precautions. To Majordomo, there can be no such thing as a
"friendly" site; all list admins must be treated with the same amount of
TN> A simpler fallback that does what Jason wants would be to extend the
TN> syntax of 'taboo' strings to allow one or more flags at the end:
But it's already been implemented that way! I'm just asking about one
final bit of semantics. (The current additional flags are line limit and