>
>Having someone gain access to your site may not be a big deal, but people tend to reuse passwords. Sending out their username and password may end up giving access to any number of other sites that the user uses. The WebSecurity class (http://msdn.microsoft.com/en-us/library/webmatrix.webdata.websecurity%28v=vs.111%29.aspx) has methods to generate a temporary token and reset the password based off of the token. It also uses hashed passwords in case there is a data breach.
>
>Implementing security like this is a lot like performing backups: it doesn't seem like its important until something goes wrong.

Yep - this is WAY more important than you might think and people DO reuse passwords like crazy. What might happen if one of those passwords happen to also be their e-mail password? Think of how many OTHER websites let you reset passwords just through e-mail (and how much information about a person is contained in e-mails). Those people would basically be screwed.