We are sending a verification e-mail and requiring an action to verify the user 
and e-mail address.  However, that is only for the people who register with us 
online.  Which currently represents less than 10% of the 25,000 email addresses 
in our system.  

The other 90+% are collected during the interview process when a donor 
registers to donate blood. My concern is not so much someone giving a bogus 
e-mail address as it is looking for typos or other errors.

Believe it or not we strated collecting e-mail addresses only about a year ago. 
 There was very little training associated with telling our interviewers to 
start collecting email addresses.  You would not believe what I am getting as 
e-mail addresses. 

Addresses like:
[EMAIL PROTECTED]
KenATyahoo

These are the easy ones to fix.  I run a simpy cfif email does not contain "@" 
or does not contain "." and I collect most of the problems.

However, as I get ready to go live I am running into smaller issues that I 
would like to be able to resolve on the front end.  

are these valid addresses?

[EMAIL PROTECTED]
[EMAIL PROTECTED]

I found what I thoguht was a pretty good regex but it does not allow for 
underscores at teh beginning or end of the first part of teh email address.  It 
also does not allow for two non-alpha numeric characters to be next to each 
other.  So I cannot be [EMAIL PROTECTED] (two underscores together).

Is this regex accurate or being more restrictive than required.  My 
understanding of RFC2822 is that most characters (!$%^&* etc..) are acceptable 
in an email address.  But then again I might not be reading it right.

PS. I'm sending a verification e-mail to [EMAIL PROTECTED]  it looks suspicious 
to me :)

-----Original Message-----
From: Spike [mailto:[EMAIL PROTECTED]

It's actually fiendishly difficult to write a regex, or even a set of 
regexes to fully validate the syntax of an email address.

Once you've done that you still have the problem of people entering 
emails like [EMAIL PROTECTED] which is almost certainly not their own.

The most reliable approach is usually to send an email that requires the 
recipient to take some action to verify that they received the message.

Beyond that, I typically use a very simple regex something like 
"[EMAIL PROTECTED]" to validate that the basic syntax could be an email address.

Spike

Confidentiality Notice:  This message including any
attachments is for the sole use of the intended
recipient(s) and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the
intended recipient, please contact the sender and
delete any copies of this message. 



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Special thanks to the CF Community Suite Gold Sponsor - CFHosting.net
http://www.cfhosting.net

Message: http://www.houseoffusion.com/lists.cfm/link=i:4:186469
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to