Streamlined process for site registration [verification of mailbox]

One of the processes you usually see is this:
1. Fill in the user name, password, duplicate password, Email 、......, submit;
2. Receive the email, click on the activation link;
3. Further improve the information or use the website.

According to the above process, please think:
"Is there a problem with the email address being tied to a username and password before the email activation link has been used?" "

Of course there is a problem, just as the bank will not yet look at your identity card, the first to send a bank card and password to you.
Now that you want to verify that the mailbox is valid, you should not bind the user name, password, and so on to the mailbox before it is successfully verified.
The normal process should be: the user through the mailbox to obtain the activation link, and then fill in "User name", "password" and other personal information, submitted to complete the registration.

What would be the problem? There are a number of problems that may exist: (note only possible)
1. A fill in the B's mailbox, B can no longer use this mailbox to register.
2. A has filled in the wrong mailbox, does not provide the change verification mailbox, a because cannot receive the activation message cannot complete the registration. (Note Because the front error, so to increase the function of remediation, but also to provide changes to verify the mailbox, product development and use is therefore inefficient)
3. b received an activation letter from someone else to write: Welcome to your dear A. b inexplicably clicked the link, found that a website has been registered, but B does not know the user name or password.
4. A fill in the wrong e-mail, b error to activate, a as usual with the user name and password use the function of the site. B is the one who receives notification messages all day.
5. C randomly fill in a lot of fake mailboxes occupy a large number of user names, resulting in a lot of usernames can no longer be used by others.
...... There may be more than one case of an error, and so on.

e-mail verification and phone verification are actually a similar situation.
We often know that when the mobile phone authentication, let the user receive the SMS Verification Code, the verification code after the user to do what he can do.
The same is true if your site is a website that only validates the validity of your mailbox. First Receive activation link, verify valid and then fill in the password and so on information.
The process for verifying a mailbox that is generally loose is:
1. Fill in the frequently used mailbox, submit, send verification link.
2. Receive the email and click on the verification link.
3. Fill in the password and other personal information, complete the registration.
Why it is easy to verify the mailbox process, because when you fill out the mailbox, you can fill in anyone's email address. You can complete the registration of your own mailbox here, you can also fill in a friend's mailbox to invite friends to register. (a function of multi-use, save the re-development of a "invite friends" function, who happened. ）

Note: There may be some problems with this loose process if the phone is verifying the registration. Because the site to send SMS verification code is also a cost, if the malicious user to fill in the various number of requests for verification will waste the resources of the site, but also for the users who receive text messages is a spam message. The easy mailbox verification process is the same, but the site sends an email to the cost of a relatively low.
Rigorous some mobile phone verification the registration process should look like this:
1. The user sends a request for registration to the website desk number.
2. The Web service desk receives instructions to send a verification code message back to the user's phone.
3. The user enters the verification code, completes the registration.

Now many of the website email server address has been a lot of mail operators as spam. In order to avoid the easy mailbox verification process, the user filled out the email authentication request, but the user to the "Junk mail Box" to receive the verification message, or simply do not receive the verification message. It is recommended to verify the registration of email authentication with a few strict mobile phone verification registration as well.
1. The user sends a message to the Web mail server requesting registration. (After the user sends a message to the server address, the server address will automatically appear in the user's "contacts", so that the server's postback messages will no longer be "spam blocking.") ）
2. The Web mail server receives an order to register, and sends back a link to complete the registration of the email.
3. The user clicks the encrypted link, fills in the password and so on personal information, completes the registration.

the above is only to verify that the mailbox is valid to use the site product site, then someone asked: if I do not verify the mailbox can also let users use some of the features of the site?

A web site that does not validate a mailbox and allows users to use some of its features is the method of registering and verifying it first.
When registering, let the user fill in: User name (login name, note Because the mailbox has not been verified to not be available.) ), password, email and other personal information, complete the registration. The basic functionality of the site users can make.
If a user fills out a mailbox at the same time, you can send a link to the mailbox-bound user name. If you do not fill in the "profile" can be filled in later, and click on the "Bind Mailbox" button, send the mailbox binding user name link. But here's toNote: When you bind a mailbox after the yourselves is completed, the page arrives after the user clicks the bind link to verify the user's identity to bind the mailbox again. That is, let the user to bind this mailbox enter their user name and password. Verify that the user name is bound to the mailbox by completing the error. Otherwise a filled in B's mailbox request binding, B casually click on the link, the result of a is bound to B's mail

Streamlined process for site registration [verification of mailbox]