Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 0.8.6
Request #8073 a@a is valid email
Submitted: 2006-06-29 14:51 UTC
From: a dot romka at gmail dot com Assigned: amir
Status: Closed Package: Validate (version 0.6.3)
PHP Version: 4.3.2 OS:
Roadmaps: 0.8.0    
Subscription  
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes. If this is not your bug, you can add a comment by following this link. If this is your bug, but you forgot your password, you can retrieve your password here.
Password:
Status:
2006-12-16 11:15 UTC
Package:
Bug Type:
Summary:
From: a dot romka at gmail dot com
New email:
PHP Version: Package Version: OS:

 

 [2006-06-29 14:51 UTC] a dot romka at gmail dot com (Romka)
Description: ------------ If you enter a@a (without .com or .whatever) - it validates as email. Test script: --------------- $vars['email'] = 'a@a'; if (empty($vars['email']) || !Validate::email($vars['email'])) { $errors['email'] = true; } var_dump($errors); Expected result: ---------------- $errors['email'] = false Actual result: -------------- $errors['email'] = true

Comments

 [2006-07-09 08:06 UTC] amir at php dot net (Amir Mohammad Saied)
According to RFC 822 it is an "Expected Behavior" (based on what I got from it) Feedbacks?
 [2006-07-21 12:51 UTC] amir at php dot net (Amir Mohammad Saied)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better. Finally we decided to mark a@a as an invalid one in non-RFC mode, surely it's still valid if (use_rfc822)