Also, another 10% of my users get the email but get stuck in an “email activation loop”, where they click the link and it takes them to a screen that tells them they need to click the link in the email to activate. Not sure why some get this and others can click with no problem.
Wondering if there is a way to disable or bypass the email activation stage. Seems like about 20% of my users get stuck here, and I know I can manually bypass them, but it would be nice to just turn this off. I know they are valid email addresses, since they are the same as I communicate with them on, but the activation email seems to be getting stuck in spam filters somewhere (some say they don’t even see the email in their junk, meaning I assume it was caught by their firewall and not even allowed into the client’s email). Thanks!
Funnily enough, I’m going through the exact same issue now!
@katie.fair @jevaaler my approach would be try and resolve the deliverability issues, rather than disable/bypass email activation (which could increase spam accounts) - during your initial Community implementation do you know if DKIM/spf was setup in the public DNS of your domain? Both of these are email validation authentication methods; having both setup will help greatly with email deliverability -essentially Community is sending the emails on your behalf from a domain that isn’t the same as your email address, so DKIM/spf serve to allow the recipient mail server to validate that Community has ‘permission’ to send these emails on your behalf, and isn’t spoofing. Many mail servers/clients will either send to spam, or block/bounce emails where either DKIM or spf validation fails.
If DKIM and spf are both set up in your public DNS and end users continue to encounter issues within the email activation process, if you have specific examples of a user (or users) signing up and encountering the issue (bonus points if you know date/time of the issue) then support should be able to check the outgoing mail client (potentially SendGrid, I think that’s what they use for CS anyway) to determine the status of the email (sent/bounced/blocked/rejected/opened, etc).
I believe our outgoing email client is Amazon Web Services. We couldn’t use SendGrid due to GDPR issues. But I can check with our IT folks if DKIM and spf are set up in our community DNS
