Development of third-party account access, if the account access is not bound to a mailbox, what is the problem?

Currently do not use a third-party account login, research several web site discovery, with sweep sweep login, all need to bind a mailbox.
However, some websites can not bind mailboxes, but they may restrict the publishing functionality.

Why do you have to bind the mailbox, since it is logged in, what will be the problem? The pit is not visible for the time being.

Reply content:

Currently do not use a third-party account login, research several web site discovery, with sweep sweep login, all need to bind a mailbox.
However, some websites can not bind mailboxes, but they may restrict the publishing functionality.

Why do you have to bind the mailbox, since it is logged in, what will be the problem? The pit is not visible for the time being.

The non-binding does not affect the user's sign-in function, which is usually the most direct purpose of the binding mailbox: "Users who log in from a third-party platform to their local users".
Other benefits of binding include:

• Localization: The user sets the password can use the mailbox to log in directly, thus reduces to the third party platform the dependence;

• Personalization: Can be sent through the mailbox like the user push feeds;

• Security: For some more sensitive operations you can do security verification through a mailbox.

