Subject: Redeem: $50 Voucher

From: $50 eGift Card <[email-masked]>
Date: Fri, 08 Aug 2014 11:42:46 -0700

ATTN: Atompub-archive
Starbucks Rewards Pending
-------------------------

Greetings Atompub-archive,

In honor of Summer We are giving you $50

To Enjoy Your Starbucks Rewards, all you need to do:

1) Visit:  http://www.lionright.com/redeem/starbucks/voucher/here.html
2) Give us your opinion 
3) Redeem your $50 before they expire 

Member Rewards Program

=
0
'
0
To stop further rewards notifications - write Daily Updated Alerts at 9306 BOVA CT
Louisville, KY 40291 or visit http://www.lionright.com/krk/fmgi93/ekg.jg90
=
+
0
 Yes, but even if it's a valid number, that doesn't mean it's an existing number, and even if it's existing, that doesn't mean that it is the users'. If it's that important, you need to set up an automated system that phones them up to check... If your budget stretches that far  yes that's true - my personal feeling here is probably affected by the fact that one of my laptops has a  agree from a usability perspective, but allowing arbitrary input may expose your website to cross-site scripting (XSS) attacks. A malicious user might be able to inject JavaScript in your free-form phone number Sometimes users have to give a valid phone number. If you state that it's part of the ToS to give one, they can't give a fake one without being in violation. If you at least make sure from a validation perspective that  usually tend to gravitate towards this way of thinking with user experience. A valid US phone number at the core is 10 digits: ^(.*\d.*){10,}$. That allows it to be entered in any w
 ay the user would like. Then, on the  But regex validation won't help you. The one and the only way to actually validate if the phone number is correct is to actually send a message to it (in case of mobile) AND make sure the user confirms using some kind of verification code. This is what you do when the number correctness is important. Everything else is just for user's convenience to protect against some (but not all) typos and does not validate anything.  well sure, I understand that, but if you can help me catch the error of leaving off a digit, it saves me the (slight) inconvenience of getting a server-side error, interpreting it, finding the field again, etc. This is a very good answer. No one is ever going to do any sort of math on phone numbers, they want communication information. The only thing forgotten is if you want to search for a phone number to see who's it There are a million use cases where this plain text solution is the answer. But there are a million use cases 
 where this would cause many many problems. Look at how you are using the phone number and why you are asking for it. Then you can decide which methodology is right for you. If you don't know why you are asking or how you are using it, you probably shouldn't be asking for a phone number in the first place.   Jason Jan 22 '13 at 19:33