You are hereHome
 Tags
  1. 5 items are tagged with SQL
  2. 2 items are tagged with Codeplex
  3. 2 items are tagged with IdentitySwitcher
  4. 2 items are tagged with Installation
  5. 2 items are tagged with Skin Object
  6. 2 items are tagged with Upgrading
  7. 1 items are tagged with AJAX Extensions
  8. 1 items are tagged with ASP.NET
  9. 1 items are tagged with debugging
  10. 1 items are tagged with email validation
  11. 1 items are tagged with Google
  12. 1 items are tagged with Inline Skin Object
  13. 1 items are tagged with intellisense
  14. 1 items are tagged with Language
  15. 1 items are tagged with moving
  16. 1 items are tagged with regex
  17. 1 items are tagged with Search Results
  18. 1 items are tagged with Skinning
  19. 1 items are tagged with SQL Server 2008
  20. 1 items are tagged with TokenReplace
  21. 1 items are tagged with Visual Studio 2008
  

Define your own e-mail validation in DNN 4.5

Last Updated 09/16/2008
By: Erik van Ballegoij

While DotNetNuke 4.4.x already validates emails in the user profile with a regular expression, this regular expression could not be changed by portal admins. In DNN 4.5, the regular expression used to validate email address can be altered in the User Settings Page (Admin > User Accounts > User Settings)

The default regular expression is:

\b[a-zA-Z0-9._%-+']+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,4}\b

And while this catches a lot of errors already, there still are some email address that will wrongfully validate, while some other valid addresses will not. For example: erik.vanballegoij@.dotnetnuke.com will validate, as will erik.vanballegoij@dotnetnuke..com, while both are not valid (punctuation errors). Also, erik@somemuseum.museum will not validate, even though it is perfectly valid.

I've found the article by Jan Goyvaerts (http://www.regular-expressions.info/email.html) very informative when it comes to validating email addresses with regular expressions. Charles Nurse probably used the same article as inspiration, as the DNN regex closely resembles the first sample on that page. Using a few of the hints in that article led me to construct the following regex:

^[a-zA-Z0-9._%-+']+@(?:[a-zA-Z0-9-]+\.)+(?:[A-Z]{2}|com|org|net|biz|info|name|aero|biz|info|jobs|museum|name)$

^[a-zA-Z0-9._%\-+']+@(?:[a-zA-Z0-9\-]+\.)+(?:[a-zA-Z]{2}|com|org|net|biz|info|name|aero|jobs|museum)$

^[a-zA-Z0-9._%\-+']+@(?:[a-zA-Z0-9\-]+\.)+(?:[a-zA-Z]{2}|aero|arpa|asia|biz|cat|com|coop|edu|gov|info|int|jobs|mil|mobi|museum|name|net|org|pro|root|tel|travel|cym|geo|post)$

(Thanks Gilles for letting me know there were a few errors in the regex.. thats what you get when copy-pasting ...) Which will correctly invalidate adresses with dot after @ and with consecutive dots. Also, all extra top level domain names will be validated.

Now, I do not consider my self a regex expert in any way, in fact, I need tools to understand them at all. I like Expresso myself, but I've also looked at RegexBuddy and The Regulator.

Now.. there's only one question left: what if i wanted to exclude some domains, like yahoo, hotmail etc. I've been trying to construct the proper regex but failed misserably ... so if anyone out there knows how to add domain exclusion.. that would be greatly appreciated!

For a full list of generic top level domains, see here: http://www.iana.org/gtld/gtld.htm

 

(crossposted from my blog on dotnetnuke.com)

Rate this:
Recent Comments
There are currently no comments. Be the first to make a comment.
 Powered By
DotNetNuke Powered! This site is proudly powered by DotNetNuke.