> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Monday 19 January 2004 13:36, Sylvain Robitaille wrote: >> I changed all occurrences (in my own copy, of course) of '(\s|-|\.)' to >> '[\s\-\.]+', in an effort to ensure that any number of any combination >> of those characters could not be used to obfuscate a known evil number. > > Lets not forget parentheses. Here is how I would have it look. > [\s(\(|\-|\)\.]+ > > Well I hope it is correct. >> >> For example, I want to match '888 - 222 - 3456', rather than only >> '888-222-3456'. > > And it would match (888) 222- 3456. > > Douglas > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.1 (GNU/Linux) > > iD8DBQFADFjsSpWn8R0Z08URApMFAJ40OL7DhEHnTIXXTPJVLH8nc+IG7wCgjHwQ > eyl58FVHChwDGhjakVWx16E=P1Aa > -----END PGP SIGNATURE-----
Hi Doug, The rules should already account for the optional ( & ) around the area codes, the (\s|-|\.) only appeared after the area code. Maybe this will have to change soon now that the rules are "in the wild" :) --example-- /\(?203\)?(\s|-|\.)(?:234(\s|-|\.)0292|286(\s|-|\.)2187)/ --example-- Hopefully they won't start writing them as (555)(555)(5555), but I guess if they do, that will also be a great spam sign! I plan on testing Sylvain's idea as well, keep the comments, questions & suggestions coming. -matt ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk