Jeremy Bettis wrote:
>
> If you want valid email addresses, SEND A CONFIRMATION EMAIL, don't make
> some arbitrary regex that has a) the chance of being broken in the first
> place, b) will need to be changed next time a RFC comes out, c) doesn't
> agree with the real world now. If the only point is to eliminate typos then
> require one @ sign and let it go at that. I don't think I would even do
> that.
I'd love to send a confirmation email but how can I send a confirmation
email to an incorrectly typed email address?
The testing of a regex should be pretty easy. Many eyes make few bugs.
:-) /me knocks on wood.
RFCs are requests for comments. They aren't automatically standards so
just because someone publishes one, doesn't mean the standard changes.
I can't fathom the standard for email addresses changing any time soon.
Also, why would you not even require an @? I'm not trying to start a
flame war; I've just never heard an argument for not requiring an @.
Thanks,
Lance Woodson
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:35:38 EDT