Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 0.8.5

Bug #7531 Email-checks need to be more RFC-compliant
Submitted: 2006-05-01 06:38 UTC Modified: 2006-12-16 06:14 UTC
From: neufeind Assigned: amir
Status: Closed Package: Validate (version 0.6.3)
PHP Version: Irrelevant OS:
Roadmaps: 0.8.0    
Subscription  


 [2006-05-01 06:38 UTC] neufeind (Stefan Neufeind)
Description: ------------ To-do: check against RFCs e.g. currently also 8-bit-chars in the username are allowed (müller@example.com), which is illegal according the the RFC. Currently a blacklist of chars is used, which might need to be extended according to the RFC and/or a 7-bit-only-check added in the first place

Comments

 [2006-06-28 02:48 UTC] muris at juris dot com (Juris)
These e-mails according to RFC822 should be valid: Abc\@def@example.com Fred\ Bloggs@example.com
 [2006-07-25 04:16 UTC] amir at php dot net (Amir Mohammad Saied)
Well, In answer to Stefan: Right, I think imap_utf7_encode can handle this. And in answer to Juris: can you point me to the right section of the RFC822 that says quoting is permitted? Quoted from RFC822: Note: In particular, quoting is NOT permitted within atoms. For example when the local-part of an addr-spec must contain a special character, a quoted string must be used. Therefore, a specification such as: Full\ Name@Domain *is not legal* and must be specified as: "Full Name"@Domain Feedbacks?
 [2006-07-27 23:00 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. Stefan's reported issue fixed.