Sorry I took so long to get back, I was at an interview > > I don't see how '*@*.aol.*' can match '[EMAIL PROTECTED]'. > > How do you account for the first '.' in the match expression? > > For that matter, can a regular expression validly begin with "*" at all? > What does that mean? > > And why would you want to match a string of zero or more @ characters?
Apparently, I'm not really explaining myself well. The match criteria is external, in a user-defined config file. like this: BANNED_USER = *@aol.com, *@*.sourceforge.net, *@*.microsoft.*, etc. The cfg entries are then split into @user, @cnames, $domain, $tld, and $cc if pertinent. THEN they are s/\*/\.\*/g. so you end up with matches like this (PSEUDOCODE): $user =~ /^$cfg_user$/ and if $user is "[EMAIL PROTECTED]" then I never get to checking the cnames, because the .com and the aol match first. Even if they didn't, I would not check the cnames because they aren't defined in the user email. I hope that clarifies things better, Grant M. _______________________________________________ Boston-pm mailing list [EMAIL PROTECTED] http://mail.pm.org/mailman/listinfo/boston-pm
