<?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: &#8220;Please Enter A Valid Email Address&#8221;</title>
	<atom:link href="http://www.usabilityblog.com/2009/03/please-enter-a-valid-email-address/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.usabilityblog.com/2009/03/please-enter-a-valid-email-address/</link>
	<description>Blogging about usability, user experience and design</description>
	<lastBuildDate>Thu, 09 Feb 2012 16:40:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: MD:SAFIN HAYDER (SHUVO)</title>
		<link>http://www.usabilityblog.com/2009/03/please-enter-a-valid-email-address/comment-page-1/#comment-10354</link>
		<dc:creator>MD:SAFIN HAYDER (SHUVO)</dc:creator>
		<pubDate>Thu, 15 Dec 2011 15:45:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilityblog.com/index.php/2009/03/25/please-enter-a-valid-email-address/#comment-10354</guid>
		<description>read</description>
		<content:encoded><![CDATA[<p>read</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TheresNoEscapingSpam</title>
		<link>http://www.usabilityblog.com/2009/03/please-enter-a-valid-email-address/comment-page-1/#comment-10348</link>
		<dc:creator>TheresNoEscapingSpam</dc:creator>
		<pubDate>Fri, 25 Nov 2011 19:18:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilityblog.com/index.php/2009/03/25/please-enter-a-valid-email-address/#comment-10348</guid>
		<description>We can thank Yahoo for aiding and abetting spammers with the feature of &quot;disposable email accounts&quot;
To add the email address to the spam portion of mail options is useless because once the address is added the spammer has already deleted that email address from their account.</description>
		<content:encoded><![CDATA[<p>We can thank Yahoo for aiding and abetting spammers with the feature of &#8220;disposable email accounts&#8221;<br />
To add the email address to the spam portion of mail options is useless because once the address is added the spammer has already deleted that email address from their account.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Guest</title>
		<link>http://www.usabilityblog.com/2009/03/please-enter-a-valid-email-address/comment-page-1/#comment-10305</link>
		<dc:creator>Guest</dc:creator>
		<pubDate>Thu, 14 Jul 2011 06:47:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilityblog.com/index.php/2009/03/25/please-enter-a-valid-email-address/#comment-10305</guid>
		<description>tutheck5@yahoo.com</description>
		<content:encoded><![CDATA[<p><a href="mailto:tutheck5@yahoo.com">tutheck5@yahoo.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeremy</title>
		<link>http://www.usabilityblog.com/2009/03/please-enter-a-valid-email-address/comment-page-1/#comment-10234</link>
		<dc:creator>jeremy</dc:creator>
		<pubDate>Wed, 13 Apr 2011 22:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilityblog.com/index.php/2009/03/25/please-enter-a-valid-email-address/#comment-10234</guid>
		<description>jzs3752@comcast.net</description>
		<content:encoded><![CDATA[<p><a href="mailto:jzs3752@comcast.net">jzs3752@comcast.net</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George dinkel</title>
		<link>http://www.usabilityblog.com/2009/03/please-enter-a-valid-email-address/comment-page-1/#comment-9678</link>
		<dc:creator>George dinkel</dc:creator>
		<pubDate>Fri, 06 Aug 2010 01:40:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilityblog.com/index.php/2009/03/25/please-enter-a-valid-email-address/#comment-9678</guid>
		<description>i want to join ecards</description>
		<content:encoded><![CDATA[<p>i want to join ecards</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mark09</title>
		<link>http://www.usabilityblog.com/2009/03/please-enter-a-valid-email-address/comment-page-1/#comment-9399</link>
		<dc:creator>mark09</dc:creator>
		<pubDate>Wed, 30 Dec 2009 10:56:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilityblog.com/index.php/2009/03/25/please-enter-a-valid-email-address/#comment-9399</guid>
		<description>&lt;a href=&quot;mailto:makhust09@gmail.com&quot; rel=&quot;nofollow&quot;&gt;makhust09@gmail.com&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p><a href="mailto:makhust09@gmail.com" rel="nofollow">makhust09@gmail.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mark09</title>
		<link>http://www.usabilityblog.com/2009/03/please-enter-a-valid-email-address/comment-page-1/#comment-9227</link>
		<dc:creator>mark09</dc:creator>
		<pubDate>Wed, 30 Dec 2009 05:56:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilityblog.com/index.php/2009/03/25/please-enter-a-valid-email-address/#comment-9227</guid>
		<description>&lt;a href=&quot;mailto:makhust09@gmail.com&quot; rel=&quot;nofollow&quot;&gt;makhust09@gmail.com&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p><a href="mailto:makhust09@gmail.com" rel="nofollow">makhust09@gmail.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eric</title>
		<link>http://www.usabilityblog.com/2009/03/please-enter-a-valid-email-address/comment-page-1/#comment-9092</link>
		<dc:creator>eric</dc:creator>
		<pubDate>Wed, 21 Oct 2009 00:33:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilityblog.com/index.php/2009/03/25/please-enter-a-valid-email-address/#comment-9092</guid>
		<description>This happens a lot using music download&lt;br&gt;&lt;a href=&quot;http://freemusicconnection.com&quot; rel=&quot;nofollow&quot;&gt;freemusicconnection.com&lt;/a&gt;&lt;br&gt;Or EZtracks&lt;br&gt;Both say gmail is invalid. How can I verify?</description>
		<content:encoded><![CDATA[<p>This happens a lot using music download<br /><a href="http://freemusicconnection.com" rel="nofollow">freemusicconnection.com</a><br />Or EZtracks<br />Both say gmail is invalid. How can I verify?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: linsenk</title>
		<link>http://www.usabilityblog.com/2009/03/please-enter-a-valid-email-address/comment-page-1/#comment-8849</link>
		<dc:creator>linsenk</dc:creator>
		<pubDate>Mon, 20 Apr 2009 04:12:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilityblog.com/index.php/2009/03/25/please-enter-a-valid-email-address/#comment-8849</guid>
		<description>I agree with you.  Every entry should have a warning asking if you really did enter the email address or other information correctly.  Then, it should let you simply enter it and then if you entered your information wrong, it is your fault.  I agree with your example of your name being one initial and not being accepted as a first name on many websites.  When designers design their websites and use forms, they should allow more than one ideal entry.  Everyone around the world has different information and we cannot expect to have every user to enter their information in one specific way.  Designers should be flexible and meet the needs of the users in the best way possible.  In this case, having a warning and a confirmation check would do the trick!</description>
		<content:encoded><![CDATA[<p>I agree with you.  Every entry should have a warning asking if you really did enter the email address or other information correctly.  Then, it should let you simply enter it and then if you entered your information wrong, it is your fault.  I agree with your example of your name being one initial and not being accepted as a first name on many websites.  When designers design their websites and use forms, they should allow more than one ideal entry.  Everyone around the world has different information and we cannot expect to have every user to enter their information in one specific way.  Designers should be flexible and meet the needs of the users in the best way possible.  In this case, having a warning and a confirmation check would do the trick!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J Todd Bennett</title>
		<link>http://www.usabilityblog.com/2009/03/please-enter-a-valid-email-address/comment-page-1/#comment-8823</link>
		<dc:creator>J Todd Bennett</dc:creator>
		<pubDate>Thu, 26 Mar 2009 14:20:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilityblog.com/index.php/2009/03/25/please-enter-a-valid-email-address/#comment-8823</guid>
		<description>My first name is also one letter... and Intuit&#039;s Tax Cut software tells me it&#039;s an invalid name. Nothing worse than a piece of software telling you that your own name is invalid!</description>
		<content:encoded><![CDATA[<p>My first name is also one letter&#8230; and Intuit&#39;s Tax Cut software tells me it&#39;s an invalid name. Nothing worse than a piece of software telling you that your own name is invalid!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://www.usabilityblog.com/2009/03/please-enter-a-valid-email-address/comment-page-1/#comment-8822</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Thu, 26 Mar 2009 04:11:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilityblog.com/index.php/2009/03/25/please-enter-a-valid-email-address/#comment-8822</guid>
		<description>&quot;Gmail has this really neat feature where you can append “+[foo]” to your email handle...&quot;&lt;br&gt;&lt;br&gt;So what?&lt;br&gt;&lt;br&gt;IE has this neat feature where you can enclose IE-only content in specialized HTML comments.  That doesn&#039;t mean it&#039;s an appropriate implementation.  So what?&lt;br&gt;&lt;br&gt;Rather than pointing to a currently-popular email provider and a &quot;neat feature&quot; they support, you should point to the document that defines the standard, which I believe is RFC 2822 for email.  Section 3.2.4 defines &quot;+&quot; (amongst many other characters that are likely considered &quot;invalid&quot; by a lot of form validators) as part of &quot;atext&quot;, which is part of the &quot;dot-atom&quot;, which is part of the &quot;local-part&quot;, the part before the @.&lt;br&gt;&lt;br&gt;I&#039;d bet that the developer of that validation system probably just wrote a regex based on what they were familiar with in terms of email addresses.  That&#039;s what happens when you don&#039;t bother to consult the standard.&lt;br&gt;&lt;br&gt;However, along with what Keijo said, RFCs at times can be very extensive in their specifications -- and it&#039;s always possible to miss something, get something wrong, etc with such complex regexes.&lt;br&gt;&lt;br&gt;WtBL, what&#039;s standard today may be obsoleted by tomorrow... but for practicality&#039;s sake, we can&#039;t just sit still for fear of breaking a future standard, can we?  Though I like the validator-override method you mentioned :)&lt;br&gt;&lt;br&gt;Aside: re: WtBL&#039;s one-letter FN... is there a standard format for names? :3</description>
		<content:encoded><![CDATA[<p>&#8220;Gmail has this really neat feature where you can append “+[foo]” to your email handle&#8230;&#8221;</p>
<p>So what?</p>
<p>IE has this neat feature where you can enclose IE-only content in specialized HTML comments.  That doesn&#39;t mean it&#39;s an appropriate implementation.  So what?</p>
<p>Rather than pointing to a currently-popular email provider and a &#8220;neat feature&#8221; they support, you should point to the document that defines the standard, which I believe is RFC 2822 for email.  Section 3.2.4 defines &#8220;+&#8221; (amongst many other characters that are likely considered &#8220;invalid&#8221; by a lot of form validators) as part of &#8220;atext&#8221;, which is part of the &#8220;dot-atom&#8221;, which is part of the &#8220;local-part&#8221;, the part before the @.</p>
<p>I&#39;d bet that the developer of that validation system probably just wrote a regex based on what they were familiar with in terms of email addresses.  That&#39;s what happens when you don&#39;t bother to consult the standard.</p>
<p>However, along with what Keijo said, RFCs at times can be very extensive in their specifications &#8212; and it&#39;s always possible to miss something, get something wrong, etc with such complex regexes.</p>
<p>WtBL, what&#39;s standard today may be obsoleted by tomorrow&#8230; but for practicality&#39;s sake, we can&#39;t just sit still for fear of breaking a future standard, can we?  Though I like the validator-override method you mentioned :)</p>
<p>Aside: re: WtBL&#39;s one-letter FN&#8230; is there a standard format for names? :3</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keijo S.</title>
		<link>http://www.usabilityblog.com/2009/03/please-enter-a-valid-email-address/comment-page-1/#comment-8821</link>
		<dc:creator>Keijo S.</dc:creator>
		<pubDate>Wed, 25 Mar 2009 22:19:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilityblog.com/index.php/2009/03/25/please-enter-a-valid-email-address/#comment-8821</guid>
		<description>I guess most of the time improper validation code is the sad result of laziness or simply just not giving a damn. However, accepting all peculiarities allowed by RFC 2822 would probably result in accepting a lot of typos, too. This guy has come up with a rather nice idea of a three-valued validation instead of the usual accept/reject logic: &lt;&lt;a href=&quot;http://www.markussipila.info/pub/emailvalidator.php&quot; rel=&quot;nofollow&quot;&gt;http://www.markussipila.info/pub/emailvalidator...&lt;/a&gt;&gt;. I haven’t seen this idea elsewhere but I think it’s pretty good.</description>
		<content:encoded><![CDATA[<p>I guess most of the time improper validation code is the sad result of laziness or simply just not giving a damn. However, accepting all peculiarities allowed by RFC 2822 would probably result in accepting a lot of typos, too. This guy has come up with a rather nice idea of a three-valued validation instead of the usual accept/reject logic: &lt;<a href="http://www.markussipila.info/pub/emailvalidator.php" rel="nofollow">http://www.markussipila.info/pub/emailvalidator&#8230;</a>&gt;. I haven’t seen this idea elsewhere but I think it’s pretty good.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Sherman</title>
		<link>http://www.usabilityblog.com/2009/03/please-enter-a-valid-email-address/comment-page-1/#comment-8820</link>
		<dc:creator>Paul Sherman</dc:creator>
		<pubDate>Wed, 25 Mar 2009 22:06:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilityblog.com/index.php/2009/03/25/please-enter-a-valid-email-address/#comment-8820</guid>
		<description>Excellent points, and I certainly appreciate the perspective! Thanks for providing that feedback.</description>
		<content:encoded><![CDATA[<p>Excellent points, and I certainly appreciate the perspective! Thanks for providing that feedback.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WtBL</title>
		<link>http://www.usabilityblog.com/2009/03/please-enter-a-valid-email-address/comment-page-1/#comment-8819</link>
		<dc:creator>WtBL</dc:creator>
		<pubDate>Wed, 25 Mar 2009 22:00:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilityblog.com/index.php/2009/03/25/please-enter-a-valid-email-address/#comment-8819</guid>
		<description>One problem with writing &quot;accurate validation code&quot; is that, even with standards, what is the definition of everything that will be valid?  What&#039;s standard today my just become a subset of what&#039;s standard tomorrow.&lt;br&gt;&lt;br&gt;I think the best solution would be for a lot of these validation checks to be warning+confirm checks.  For example, &quot;that doesn&#039;t look like a valid email address, are you sure that&#039;s what you want to enter?&quot;  And give the user a chance to override the validation filter which may be broken.  At that point, if they don&#039;t get email&#039;s it&#039;s their own fault.&lt;br&gt;&lt;br&gt;I have a single letter of a first name.  I hate that so many systems don&#039;t allow a 1 letter first name.  It&#039;s my legal name (even if I don&#039;t go by it).  Some systems can be tricked into working if I enter a period after it making it look like an initial, but some still insist on more than two characters or that a first name not have anything that&#039;s not a letter in it.  if they were to adopt a model of saying, &quot;hey, it looks like you might have missed a few letters, are you sure that&#039;s what you want to enter?&quot;  it would avoid the problem.</description>
		<content:encoded><![CDATA[<p>One problem with writing &#8220;accurate validation code&#8221; is that, even with standards, what is the definition of everything that will be valid?  What&#39;s standard today my just become a subset of what&#39;s standard tomorrow.</p>
<p>I think the best solution would be for a lot of these validation checks to be warning+confirm checks.  For example, &#8220;that doesn&#39;t look like a valid email address, are you sure that&#39;s what you want to enter?&#8221;  And give the user a chance to override the validation filter which may be broken.  At that point, if they don&#39;t get email&#39;s it&#39;s their own fault.</p>
<p>I have a single letter of a first name.  I hate that so many systems don&#39;t allow a 1 letter first name.  It&#39;s my legal name (even if I don&#39;t go by it).  Some systems can be tricked into working if I enter a period after it making it look like an initial, but some still insist on more than two characters or that a first name not have anything that&#39;s not a letter in it.  if they were to adopt a model of saying, &#8220;hey, it looks like you might have missed a few letters, are you sure that&#39;s what you want to enter?&#8221;  it would avoid the problem.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

