I had some very helpful input from Cal Henderson on interpreting RFC 2822. I’ve included his latest validator in my head-to-head comparison and updated the test suite to reflect the consensus from our discussion.

I’ve also updated my own routine so that it still passes all the tests, of which there are now 158. As always, the full analysis is on my website and the latest version of the source code will always be in Google Code.

I would really appreciate it if you find a valid address that fails my validator, or an invalid one that passes, if you would get in touch with me and let me know.

Here are the latest scores:

Dominic Sayers: 100% validated correctly
Simon Slick: 91%
Cal Henderson: 84%
Phil Haack: 80%
Dave Child: 79%

I know Cal is working on IPv6 validation so this may change soon.

RFC nerd notes

There are two principle changes in this version.

Firstly, I now accept Dave Child and Cal Henderson’s opinion that a backslash can escape anything in a quoted string local element. However, it must escape something – it can’t be at the end of the string.

Secondly, if the string is not quoted then the local element must be a vanilla atom. You can’t escape individual characters unless the element is surrounded by double quotes.

By “local element” I mean a single component of a dot-delimited local part.

I’ve extracted the raw specification of a valid email address in BNF (Backus-Naur form) from RFC 5322 and put it here: The BNF from RFC 5322 defining parts of a valid email address. If you try to follow this in the RFC you end up going backwards and forwards and getting confused – it’s much easier to understand in the way I’ve laid it out.

Quick links: Source code | Email address validators head-to-head

OK, after some correspondence with Dave Child and Cal Henderson I have now released version 1.0 of my PHP email address validator.

This version passes all 139 unit tests in the suite – tests I have collated from RFC 3696 and from articles by Dave Child, Doug Lovell and Phil Haack plus some of my own to test the IPv6 address format. The full analysis is on my website and the latest version of the source code will always be in Google Code.

I would really appreciate it if you find a valid address that fails my validator, or an invalid one that passes, if you would get in touch with me and let me know.

Here are the scores on the doors:

Dominic Sayers: 100% validated correctly
Simon Slick: 86%
Dave Child: 81%
Phil Haack: 79%
Cal Henderson: 71%

For the RFC nerds, this version now correctly validates the obsolete local form of word *(“.” word). In other words you can regard the local part of the address as a dot-delimited series of elements each of which can be separately quoted. This means that first.”last”@example.com is now recognised as a valid address.

Quick links: Source code | Email address validators head-to-head

I’ve discovered a number of other public-domain functions that attempt to validate the format of an email address. I tried to validate my 124 test cases against these functions with the results below:

Dominic Sayers: 100% correctly validated
Simon Slick: 88% 
Dave Child: 80%
Cal Henderson: 72%

Interestingly, all the other functions failed correctly to validate the example addresses given in RFC3696 (Section 3: Restrictions on email addresses).

I couldn’t include Doug Lovell’s function in my tests because the code is copyright All Rights Reserved by Linux Journal (ironically).

Some of the other functions also supply test cases; I’ve added these to my test suite. More analysis and commentary here: RFC-compliant email address validator.

In summary, I recommend you use my function if you want totally RFC-compliant address validation.

Quick links: Source code | Email address validators head-to-head