PEAR is archived and read-only

This mirror preserves historical PEAR package releases and metadata so existing references remain available.

Home » Validate » Validate » Bug #8073

a@a is valid email

Details

Request #8073a@a is valid email
Submitted2006-06-29 14:51 UTC
Froma dot romka at gmail dot com
Assignedamir
StatusClosed
PackageValidate
PHP Version4.3.2
Roadmaps0.8.0

Comments

[2006-06-29 14:51 UTC] a dot romka at gmail dot com

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

[2006-07-09 08:06 UTC] amir at php dot net

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

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)