On Tue, Aug 08, 2000 at 10:03:50AM -0400, Charles Daminato wrote:
> It may or may not be changed, but instructions to the end user will be
> more clear.
>
> What we didn't want in this field is just a number - a number in a
> database doesn't mean much without context.
>
> As for the invalid email - it checks for alphanumeric, periods, an @, and
> a qualifying domain (well, xxx.xx at least)
You made me want to cry for a moment.
Thankfully, what you really check for is "not more than one @",
"no two dots in a row", "no @. or .@", and "doesn't start with a .".
Then you require at least one character before the @, and what you
consider a valid domain after it.
Remember, fred&[EMAIL PROTECTED], *@qz.to, and
[EMAIL PROTECTED] are all valid e-mail addresses.
Excerpted from perlfaq9:
How do I check a valid mail address?
You can't, at least, not in real time. Bummer, eh?
Without sending mail to the address and seeing whether
there's a human on the other hand to answer you, you
cannot determine whether a mail address is valid. Even if
you apply the mail header standard, you can have problems,
because there are deliverable addresses that aren't
RFC-822 (the mail header standard) compliant, and
addresses that aren't deliverable which are compliant.
I'm ok with the check there now, but I hope nobody tries to get too
"clever" and make it more inappropriately strict.
--
Christopher Masto Senior Network Monkey NetMonger Communications
[EMAIL PROTECTED] [EMAIL PROTECTED] http://www.netmonger.net
Free yourself, free your machine, free the daemon -- http://www.freebsd.org/
