>> 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-- > > My main issue with your syntax is that if you really want to not include > () and multiple instances, you could use [\s\-\.] instead of (\s|-|\.). > the [] syntax is *much* faster (according to various perlre things I've > read) > > Personally, I'd go for catching as much as possible, and go with > [\s\(\)\-\.]+ (heck, I would probably go as far as just doing \W+ or \W* > to catch any characters the spammers might try to throw in). > > -- > Chris Petersen
Chris, I'm testing an alternate set with "[\s\(\)\-\.]+" now, so far so good. I'll also take a look at \W+ and \W* to see if it looks like they could FP on attachments or such. Thanks for the syntax tips -matt "Can't wait to see what phone numbers in spam will look like in a few weeks" ;) ------------------------------------------------------- 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