I think this partly overstates the complexity of validating an e-mail address in a registration form or similar. If your aim is only to get a syntactically corr

I think this partly overstates the complexity of validating an e-mail address in a registration form or similar. If your aim is only to get a syntactically correct address to which you can try to deliver mail to, you don't need to accept stuff like: * "Name surname" <address@example.com> * Name surname <address@example.com> * Group name: Member 1 <one@member.com>, "2, member2"<two@member.com>, three@member.com * guy@nonpubliclyresolvabledomain There are many other RFC2822-valid kind of addresses that you don't need to accept if you are not writing an e-mail client, SMTP server, or similia.