> sanitising code written... On another hand, sanitising code could prove usefull in general in the future, to check just any new rule added to SA.
> Could easily lead to >deliberate of accidental DoS attacks against the machine hosting >the CGI. Ressource limitation could be enforced I guess. And a user registration, with sending back the results by email. In fact testing a rule on a full corpus woudl take so much time anyway that an HTTP connection would timeout, so response by email sounds like the only valid solution to me. That allows running the test in background, at low priority. Olivier ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Oh, it's good to be a geek. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
