> No, it doesn't. There have meen numerous long discussions in various Perl > newsgroups about the topic, and the conclusion is that you shouldn't try > to match e-mail addresses with a regular expression of your own, but use > the Email::Valid Perl module instead (or a similar module which does it > right, if you're using another language).
Unfortunately, I'm not using perl - just perlre. But I'll poke around and see what's so special about it, and if there is a similar module for php. > Have a look for the third occurrance of "RFC822PAT" in > http://search.cpan.org/src/MAURICE/Email-Valid-0.15/Valid.pm > to understand the complexity of the RFC 822 e-mail address syntax. ;-) So I see. luckily, my regex will catch 99.999% of the world, which is enough for a small ecommerce site, and better than sites that only allow the [EMAIL PROTECTED] (yes, I know it's not quite right) type pattern. As I said, I don't even think courier knows what to do with some rfc 822 addresses. > So what about ".aero" and ".museum"? No, I don't think hard-coding a list > of valid TLDs is a good idea. This is for my own stuff, I'll hard-code as I please, since it will prevent people from typing in [EMAIL PROTECTED] As for those other TLD's, I've never heard of them, but will add them (and from a quick search, looks like I need to add arpa, pro, name and coop, too) -Chris ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
