Title: sds
Name: sasd
Date: 6/2/2015 12:50:00 AM
Comment:
w
Title: sds
Name: sasd
Date: 6/2/2015 12:49:23 AM
Comment:
w
Title: Useful Code
Name: Patni - WebManager
Date: 4/9/2009 2:30:26 AM
Comment:
Fine regex pattern to match my use. :)
Title: Useful Code
Name: Patni - WebManager
Date: 4/9/2009 2:29:08 AM
Comment:
Fine regex pattern to match my use. :)
Title: Useful Code
Name: Patni - WebManager
Date: 4/9/2009 2:28:40 AM
Comment:
Fine regex pattern to match my use. :)
Title: Error
Name: frozenfrog
Date: 12/9/2008 3:06:45 AM
Comment:
Allows .@ which is quite common that users enter. Also allows characters other than a...z, 0...9 (which apparently will be allowed in the future)
Title: I think it's good
Name: escanive
Date: 9/8/2008 4:55:30 PM
Comment:
Although it might not accept some of those wacky e-mail adresses mentioned by pinetree, I find this regex pattern to match my use. Thanks.
Title: More valid addresses for which this fails
Name: Tim Lesher
Date: 5/22/2006 2:54:06 PM
Comment:
[email protected]
Title: Missing valid parts
Name: Matthew
Date: 2/14/2006 11:49:32 PM
Comment:
This does not match quoted string parts or ip address.
Title: Fails to match the valid email address
Name: The Fred and Barney Comedy Team <fred&[email protected]>
Date: 1/26/2005 3:31:18 AM
Comment:
Fails to match the valid email address
fred&[email protected]
Title: only it doesn't work
Name: pinetree
Date: 6/16/2003 4:00:12 PM
Comment:
Except that per RFC 822 (http://www.w3.org/Protocols/rfc822/Overview.html), the following email addresses are valid but would be trapped as invalid by this code. Specifically, look at Appendix A (http://www.w3.org/Protocols/rfc822/Overview.html#z10), section A.3.3.<br><br>
"Some Silly User"@example.com<br>
Another'[email protected]<br>
Yet/Another/Wacky/[email protected]
