Confirming account through studio
Currently there is a thread in which Molosser Dogs is trying to manually confirm accounts. Several of us here have tried to help, but so far no luck due to unable to make code changes. Here is the thread https://una.io/page/view-discussion?id=4576. Chris brought up a good point, which we should be able to confirm accounts in studio. Can UNA please make these changes, thank you!
-
An easy update will be for the una core to send 2 confirmation emails. One to user and one to admin. So it can be confirmed by admin, should the need arise.
-
This is something u r working on?
-
Not sure if this helps but a simple way to verify accounts is directly in the database. The details (table, column etc) is obvious but I can post if you need.
-
Did you see this ticket? https://github.com/unaio/una/issues/2499
-
Manual confirmation of user emails is not available as a standard feature, because it is not a legitimate practice. The email account owner absolutely has to confirm their email from their inbox. As an admin, you can resend confirmation emails, setup transaction email server to insure better deliverability and you can directly contact the email hosted to assist them with the confirmation process.
There are situations when the email owner is known to the site operator, or the site operator may be receiving separate letters expressly confirming one's email ownership. In such cases the best thing to do is to resend a confirmation letter and send a personal note to the email owner asking them to confirm via a confirmation email.
Opting-in emails manually may be illegal. Please, refer to https://www.ftc.gov/tips-advice/business-center/guidance/can-spam-act-compliance-guide-business - you may be fined for over $42,000 for EVERY email violation, and unless you have evidence of expressed record of email owner opting-in via Confirmation link from within their email, you may not be able to prove that your emails are sent legitimately.
----
Having said that, I agree that there may be situations when for some reason manual email confirmation is useful - for example for testing purposes for admins, allowing to create multiple test accounts quickly. So, we have added this feature in v11 and already implemented ( https://github.com/unaio/una/issues/2499 ) in CI, but I reiterate that it is not intended for and is not recommended for manually confirming standard users emails.
-
That is not the preferred method. It should be an option in the accounts section of the ACP. There is already. Change email. Resend confirmation, delete etc. Why not add confirm there also.
Admin gets many emails on a busy site. Too much work.
-
We added it in v11 already, but, like I said, even if it's a lot of work to handle it differently, admin should not be confirming users emails unless they have a proof of opt-in. It is illegal.
-
Yeah. This is so funny. I will be a millionaire next week for all the spam emails I get without opting in.
All other community and social scripts have this feature. I am happy to kmow that it is committed in v11.
Thanks Andrew Boon and UNA team.
-
Manual confirmation of user emails is not available as a standard feature, because it is not a legitimate practice. The email account owner absolutely has to confirm their email from their inbox. As an admin, you can resend confirmation emails, setup transaction email server to insure better deliverability and you can directly contact the email hosted to assist them with the confirmation process.
There are situations when the email owner is known to the site operator, or the site operator may be receiving separate letters expressly confirming one's email ownership. In such cases the best thing to do is to resend a confirmation letter and send a personal note to the email owner asking them to confirm via a confirmation email.
Opting-in emails manually may be illegal. Please, refer to https://www.ftc.gov/tips-advice/business-center/guidance/can-spam-act-compliance-guide-business - you may be fined for over $42,000 for EVERY email violation, and unless you have evidence of expressed record of email owner opting-in via Confirmation link from within their email, you may not be able to prove that your emails are sent legitimately.
----
Having said that, I agree that there may be situations when for some reason manual email confirmation is useful - for example for testing purposes for admins, allowing to create multiple test accounts quickly. So, we have added this feature in v11 and already implemented ( https://github.com/unaio/una/issues/2499 ) in CI, but I reiterate that it is not intended for and is not recommended for manually confirming standard users emails.
Dolphin had this feature and I have used it when members were not getting the emails and contacted the site. Spam mail is not the same as an email confirmation; Andrew, don't scare members with this misinformation. Perhaps someone can do a hack or a module/app to add this feature.
-
The feature is already added in v11. I just need to make sure that people understand when to use it and when not to.
-
We added it in v11 already, but, like I said, even if it's a lot of work to handle it differently, admin should not be confirming users emails unless they have a proof of opt-in. It is illegal.
NO, IT IS NOT ILLEGAL.
-
That is my understanding of the CAN-SPAM act. You can only send transactional/relationship emails with prior agreement, And the only way to reliably verify that you have such agreement is through a user-initiated confirmation.
I am not a legal advisor, so prefer to Stay on the safe side here. Like I said, the feature is developed in v11 and webmasters should use it only when it is appropriate.
To give you a typical example - we built a site for an event venue, the venue collects patrons emails on paper. The site webmaster adds emails to database and believes that since emails were expressly given it is OK to confirm them manually. That is of course incorrect, because there is no way to know if these emails indeed belong to the patrons, if they indeed still want to receive emails or if there were any spelling errors. All emails have to be confirmed by users.
-
To clarify the request I made, I mentioned being able to confirm a member's email address via the Studio and THAT'S IT. The member has the option to receive site newsletters and or not at the time they setup their account. If they choose to leave it turned on or to turn it off is THEIR choice and should NOT be changed. This has nothing to do with getting their email confirmed AFTER they have signed up. The reason I suggested this is because it's possible that your site could be "blocked" by spam listings, by the ISP, and/or the mail/exchange domain delivering the email. Some of these things you may not have control of so, in order for the user to utilize the functionality of the site, you could assist them in confirming the email for them. This should NEVER be done without the member's consent via email or some type of direct communication. Hence the reason all admins should advise their users of how they can contact the admin/site for assistance.
As a webmaster/admin, you should NEVER........EVER.... change a members information or settings at your site. If a member is asking you to make changes for them, you should respond with instructions advising the member how "they" can do it if they choose. Regardless of the legalities on "what" can and cannot be done as a webmaster/admin, any member can 'choose' to file a civil suit against you for altering any of their information or settings without written consent. Whether they win or not is irrelevant so, it's best to just NOT do it and save yourself the possible headaches.
FYI - If your members are having that hard of a time receiving emails from your site, then maybe you should install the SMTP module and use a 3rd party mailing service and your chance of having to manually confirm an email is greatly reduced (like I did). I posted a topic HERE for MailJet which works well and not too expensive.
-
Of course this should only be used as an emergency and carefully. Any admin/webmaster that plans on doing this just for the heck of it, will be looking for.....
-
-
Come on all. This is ridiculous. Admin has total control of their site and can approve, delete, ban, whatever. This is getting too complicated. Do you know how many mailing lists you are on? There are still agencies, companies, who sell email addresses.
Why is it that when I turned 50 I started getting emails from AARP, AMAC, and every damn Geriatric peddling company that exists. I did not confirm some kind of registration or opt-in. They all have the unsubscribe or opt-out at the bottom and I dutifully click them. I am sure that confirms that my email address is valid and puts me on some other damn list.
Where has reason gone?
-
Come on all. This is ridiculous. Admin has total control of their site and can approve, delete, ban, whatever. This is getting too complicated. Do you know how many mailing lists you are on? There are still agencies, companies, who sell email addresses.
Why is it that when I turned 50 I started getting emails from AARP, AMAC, and every damn Geriatric peddling company that exists. I did not confirm some kind of registration or opt-in. They all have the unsubscribe or opt-out at the bottom and I dutifully click them. I am sure that confirms that my email address is valid and puts me on some other damn list.
Where has reason gone?
Damn I'm 48 and I get tons of spam emails, same as you. There is no more privacy anymore, sucks, but I agree with u.
-
I want to manage users' accounts. such as the user's manual password change, e-mail change, deletion of the user. I understood from the articles I read above. i don't know right una does not allow users to be deleted or edited on our site. do I understand the truth?
-
Hello MuhammeT !
We have similar ticket about it https://github.com/unaio/una/issues/2559 . Also, the edit emails possibility UNA has already.
