<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Check Email Address with JavaScript and Regular Expressions</title>
	<atom:link href="http://marketingtechblog.com/2007/10/28/javascript-regex-emailaddress/feed/" rel="self" type="application/rss+xml" />
	<link>http://marketingtechblog.com/2007/10/28/javascript-regex-emailaddress/</link>
	<description>new media strategies and other marketing gems</description>
	<lastBuildDate>Mon, 06 Jul 2009 17:14:21 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Adnan</title>
		<link>http://marketingtechblog.com/2007/10/28/javascript-regex-emailaddress/comment-page-1/#comment-286692</link>
		<dc:creator>Adnan</dc:creator>
		<pubDate>Tue, 23 Jun 2009 13:33:01 +0000</pubDate>
		<guid isPermaLink="false">http://marketingtechblog.com/2007/10/28/javascript-regex-emailaddress/#comment-286692</guid>
		<description>Can you please explain the regular expression of this code and how its working? Also about .test - Is .test a default statement in javascript to check things like you did in the code above?</description>
		<content:encoded><![CDATA[<p>Can you please explain the regular expression of this code and how its working? Also about .test &#8211; Is .test a default statement in javascript to check things like you did in the code above?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gheesh</title>
		<link>http://marketingtechblog.com/2007/10/28/javascript-regex-emailaddress/comment-page-1/#comment-282736</link>
		<dc:creator>Gheesh</dc:creator>
		<pubDate>Sun, 24 May 2009 16:47:09 +0000</pubDate>
		<guid isPermaLink="false">http://marketingtechblog.com/2007/10/28/javascript-regex-emailaddress/#comment-282736</guid>
		<description>Just a small correction: The regular expression has an extra ()+ at the end. It should read:

^([a-zA-Z0-9_\.\-])+\@(([a-zA-Z0-9\-])+\.)+[a-zA-Z0-9]{2,4}$

With the first one any length TLDs would be accepted (which is not intrinsecally wrong as others have pointed out, but if that was the intention the expression could be shortened).</description>
		<content:encoded><![CDATA[<p>Just a small correction: The regular expression has an extra ()+ at the end. It should read:</p>
<p>^([a-zA-Z0-9_\.\-])+\@(([a-zA-Z0-9\-])+\.)+[a-zA-Z0-9]{2,4}$</p>
<p>With the first one any length TLDs would be accepted (which is not intrinsecally wrong as others have pointed out, but if that was the intention the expression could be shortened).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robby Slaughter</title>
		<link>http://marketingtechblog.com/2007/10/28/javascript-regex-emailaddress/comment-page-1/#comment-271698</link>
		<dc:creator>Robby Slaughter</dc:creator>
		<pubDate>Mon, 16 Mar 2009 19:34:47 +0000</pubDate>
		<guid isPermaLink="false">http://marketingtechblog.com/2007/10/28/javascript-regex-emailaddress/#comment-271698</guid>
		<description>It also doesn&#039;t appear to handle the plus character, which is valid. 

See: http://www.dominicsayers.com/isemail/

On a larger note, this is a key problem with cutting-and-pasting code, one which deserves a full discussion in itself.

@robbyslaughter.com</description>
		<content:encoded><![CDATA[<p>It also doesn&#8217;t appear to handle the plus character, which is valid. </p>
<p>See: <a href="http://www.dominicsayers.com/isemail/" rel="nofollow">http://www.dominicsayers.com/isemail/</a></p>
<p>On a larger note, this is a key problem with cutting-and-pasting code, one which deserves a full discussion in itself.</p>
<p>@robbyslaughter.com</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pande</title>
		<link>http://marketingtechblog.com/2007/10/28/javascript-regex-emailaddress/comment-page-1/#comment-271517</link>
		<dc:creator>Pande</dc:creator>
		<pubDate>Sun, 15 Mar 2009 00:30:31 +0000</pubDate>
		<guid isPermaLink="false">http://marketingtechblog.com/2007/10/28/javascript-regex-emailaddress/#comment-271517</guid>
		<description>Would be fine if we could find a solution to avoid fake e-mail addresses on comments on  Wordpress</description>
		<content:encoded><![CDATA[<p>Would be fine if we could find a solution to avoid fake e-mail addresses on comments on  Wordpress</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sanjay</title>
		<link>http://marketingtechblog.com/2007/10/28/javascript-regex-emailaddress/comment-page-1/#comment-251467</link>
		<dc:creator>sanjay</dc:creator>
		<pubDate>Tue, 02 Dec 2008 15:42:45 +0000</pubDate>
		<guid isPermaLink="false">http://marketingtechblog.com/2007/10/28/javascript-regex-emailaddress/#comment-251467</guid>
		<description>Just an FYI; I haven&#039;t tried Ade&#039;s solution but the pattern above doesn&#039;t validate e-mail addresses with apostrophes in them.. (eg, Mike.O&#039;Hare@Whatever.com).  Apostrophes are valid per the RFC 2821/2822 --&gt; http://www.faqs.org/rfcs/rfc2822.html

HTH,
Sanjay</description>
		<content:encoded><![CDATA[<p>Just an FYI; I haven&#8217;t tried Ade&#8217;s solution but the pattern above doesn&#8217;t validate e-mail addresses with apostrophes in them.. (eg, Mike.O&#8217;Hare@Whatever.com).  Apostrophes are valid per the RFC 2821/2822 &#8211;&gt; <a href="http://www.faqs.org/rfcs/rfc2822.html" rel="nofollow">http://www.faqs.org/rfcs/rfc2822.html</a></p>
<p>HTH,<br />
Sanjay</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Szubu - LorenB</title>
		<link>http://marketingtechblog.com/2007/10/28/javascript-regex-emailaddress/comment-page-1/#comment-224365</link>
		<dc:creator>Szubu - LorenB</dc:creator>
		<pubDate>Sun, 05 Oct 2008 06:16:40 +0000</pubDate>
		<guid isPermaLink="false">http://marketingtechblog.com/2007/10/28/javascript-regex-emailaddress/#comment-224365</guid>
		<description>btw, I really like what you have going on here, your tutorials are very simple, I will definately be bookmarking this one....</description>
		<content:encoded><![CDATA[<p>btw, I really like what you have going on here, your tutorials are very simple, I will definately be bookmarking this one&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Szubu</title>
		<link>http://marketingtechblog.com/2007/10/28/javascript-regex-emailaddress/comment-page-1/#comment-224362</link>
		<dc:creator>Szubu</dc:creator>
		<pubDate>Sun, 05 Oct 2008 06:10:12 +0000</pubDate>
		<guid isPermaLink="false">http://marketingtechblog.com/2007/10/28/javascript-regex-emailaddress/#comment-224362</guid>
		<description>Hi there,

I am tring to use this in an existing form in real-time, but this doesnt appear to be validating in realtime like your password strength checker...

Or, am i just that clueless, and it aint workin for me?</description>
		<content:encoded><![CDATA[<p>Hi there,</p>
<p>I am tring to use this in an existing form in real-time, but this doesnt appear to be validating in realtime like your password strength checker&#8230;</p>
<p>Or, am i just that clueless, and it aint workin for me?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gemp</title>
		<link>http://marketingtechblog.com/2007/10/28/javascript-regex-emailaddress/comment-page-1/#comment-189833</link>
		<dc:creator>gemp</dc:creator>
		<pubDate>Thu, 07 Aug 2008 14:25:02 +0000</pubDate>
		<guid isPermaLink="false">http://marketingtechblog.com/2007/10/28/javascript-regex-emailaddress/#comment-189833</guid>
		<description>There&#039;s much simpler way to write the expression:
&lt;code&gt;var regex = /^[a-z0-9\._-]+@([a-z0-9_-]+\.)+[a-z]{2,6}$/i;&lt;/code&gt;
- With the final modifier /i there&#039;s no need to indicate the upper case range.
- I don&#039;t know of any &lt;acronym&gt;TLD&lt;/acronym&gt; with numbers in it.
On a side note, I do allow TLD with up to 6 chars; new ones arrive regularly and you never know (well, somme future ones may even have numbers in it, I know).</description>
		<content:encoded><![CDATA[<p>There&#8217;s much simpler way to write the expression:<br />
<code>var regex = /^[a-z0-9\._-]+@([a-z0-9_-]+\.)+[a-z]{2,6}$/i;</code><br />
- With the final modifier /i there&#8217;s no need to indicate the upper case range.<br />
- I don&#8217;t know of any <acronym>TLD</acronym> with numbers in it.<br />
On a side note, I do allow TLD with up to 6 chars; new ones arrive regularly and you never know (well, somme future ones may even have numbers in it, I know).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Android</title>
		<link>http://marketingtechblog.com/2007/10/28/javascript-regex-emailaddress/comment-page-1/#comment-181477</link>
		<dc:creator>Android</dc:creator>
		<pubDate>Thu, 24 Jul 2008 10:32:50 +0000</pubDate>
		<guid isPermaLink="false">http://marketingtechblog.com/2007/10/28/javascript-regex-emailaddress/#comment-181477</guid>
		<description>Perfect, just what I needed!</description>
		<content:encoded><![CDATA[<p>Perfect, just what I needed!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Douglas Karr</title>
		<link>http://marketingtechblog.com/2007/10/28/javascript-regex-emailaddress/comment-page-1/#comment-61744</link>
		<dc:creator>Douglas Karr</dc:creator>
		<pubDate>Fri, 02 Nov 2007 15:23:04 +0000</pubDate>
		<guid isPermaLink="false">http://marketingtechblog.com/2007/10/28/javascript-regex-emailaddress/#comment-61744</guid>
		<description>Hi Reg,

You can test out the Regex utilizing an &lt;a href=&quot;http://www.quanetic.com/regex.php&quot;&gt;Online Regex Tester&lt;/a&gt;.

Also, there&#039;s definitely much more that can be done if you want to ensure an &lt;a href=&quot;http://www.douglaskarr.com/2006/12/06/valid-email-address-length/&quot;&gt;email address&lt;/a&gt; is valid in accordance with the RFC.  

There are a few reasons not to allow someone to enter an invalid email address:
1.  They will get annoyed at you when the email they expected doesn&#039;t get through - regardless of whether or not it was your fault the address was entered incorrectly.
2.  If com.museum was a valid domain and, let&#039;s say, Yahoo! operated it - any email address that bounced would have a negative impact on your company&#039;s reputation for email delivery.  This could lead to all of your company&#039;s email being blocked.
3.  If your email service provider allowed you to enter bob@com.museum, you&#039;d also pay for each email sent to that email address until they unsubscribed that address due to bounces.  I would steer clear of any ESP that would allow an invalid email address like that - they&#039;re just taking your money!

Thanks for stopping by!
Doug</description>
		<content:encoded><![CDATA[<p>Hi Reg,</p>
<p>You can test out the Regex utilizing an <a href="http://www.quanetic.com/regex.php">Online Regex Tester</a>.</p>
<p>Also, there&#8217;s definitely much more that can be done if you want to ensure an <a href="http://www.douglaskarr.com/2006/12/06/valid-email-address-length/">email address</a> is valid in accordance with the RFC.  </p>
<p>There are a few reasons not to allow someone to enter an invalid email address:<br />
1.  They will get annoyed at you when the email they expected doesn&#8217;t get through &#8211; regardless of whether or not it was your fault the address was entered incorrectly.<br />
2.  If com.museum was a valid domain and, let&#8217;s say, Yahoo! operated it &#8211; any email address that bounced would have a negative impact on your company&#8217;s reputation for email delivery.  This could lead to all of your company&#8217;s email being blocked.<br />
3.  If your email service provider allowed you to enter <a href="mailto:bob@com.museum">bob@com.museum</a>, you&#8217;d also pay for each email sent to that email address until they unsubscribed that address due to bounces.  I would steer clear of any ESP that would allow an invalid email address like that &#8211; they&#8217;re just taking your money!</p>
<p>Thanks for stopping by!<br />
Doug</p>
]]></content:encoded>
	</item>
</channel>
</rss>
