Subject: STOP paying for expensive auto repairs

From: NationalRepairCenter <[email-masked]>
Date: Mon, 18 Aug 2014 12:34:22 -0700

How would you like to NEVER pay for another auto repair? 

Sound too good to be true? It's not! 

With an Auto Protection Plan from NoMoreAutoBills you don't have to worry about expensive bills such as these: 

- $2000 for a new air conditioner
- $300 for a new alternator
- $4000 for blown engine! 

We pay ALL of your auto repair bills with NO HASSLE. 

CLICK Here -> http://www.tonestraight.com/reverse/payment/auto/id333.index

We will also pay for other related items such as: 

- Car Rentals
- Lockout Assistance
- Towing
- and many more! 

-
-
=
-
To stop further notifications - write Daily Updated Alerts
9306 BOVA CT
Louisville, KY 40291 or visit http://www.tonestraight.com/ekgj/jgur504.solig
-
=
-
1 I was going to post the following update to the original eval answer as follows: new Date(parseInt(data.DateTime.replace(/\/Date\((\d+)\)\//gi, "$1"))); but then I found this answer which will be much faster replace function is safer in case MS decides to change the format. Both methods (the replace function and this answer) would have to change if MS changes the format.    Does this work with the +- suffixes found sometimes like 1224043200000-0600   Lee Whitney Feb 21 
@LeeWhitney: Yes, but it will ignore the suffix (which is a timezone offset). The parseInt function grabs numerals from the front of the string passed to it until it encounters a non-numeral character or the end of the string, at which point it stops and returns the numeric result.   Roy Tinker Feb 22 '12 at 17:13 
Lose timezone information though.you please update it with the radix var date = for my question but where is this new Date() from ?he Date() class is built into javascript.  without a radix is a crime! Please add the radix Eval = Evil. ParseInt sans radix is bad. But no eval trumps that. Every rule has exceptions, and I think this is when an exception applies. The JSON date numbers from .NET never have a leading "0", so we can safely leave out the radix. see my reply to JamesKyburz It's worth noting that this date format is pretty bad and the general move is to ISO-8601 formatted dates in Good answer, its a universal issue, I did it for m