You left out the most important detail - Is validation neccessary for WHAT?
Are you trying to avoid sending emails to an invalid email account? Are you trying to avoid fake signups?
What goal are you trying to acheive?
If it is validation for the sake of validation, then my answer is that I accept nothing less than the best.
raghavan20 wrote:Q1. How many of you think that we should validate for the last part of the email address?
If you are trying to avoid invalid email accounts, or fake signups, then yes, you need to validate the entire email address. Not doing so means you aren't validating - you are testing portions of the email address.
raghavan20 wrote:Q2. If you think we should validate, what are the conditions you would impose to be complied?
I'll make it very easy for you.. here is my RFC-compliant function for validating email addresses:
http://svn.gna.org/viewcvs/blacknova/tr ... iew=markup
It takes an email address as its only input, and returns true or false, depending on its validity.
Please note, there is a difference between
validating that an email is RFC-compliant (what my class does), and
discovery of a valid email address from the server (which is unreliable at best).
For my game, the goal was to prevent invalid email addresses, so we wouldn't send emails to places that didn't exist. The fact that our signup sends a shared secret ensures that they will use an actual account, we just wanted to prevent typo's and the like.