When the following is true:
- User attempts to create an account
- Instance has “require registration application” enabled
- Instance’s email is not working/unavailable
the application seems to get lost, the user never receives an email (even after email functionality is restored), nor can that email/username be used going forward to re-submit the account creation request.
Additionally, since the user never verifies their email, the instance admin never gets a registration application.
It’s not currently an issue for me, however, would it be possible to delete these ghost users? If you lookup the profile/username in the database, you can view it via the web UI, but the only options appear to be either blocking the user or banning them. It might be good to be able to completely delete the accounts, no?
My problem with email was a transient issue in resolving “smtp.sendgrid.net” inside my Kubernetes cluster.
I think setting up a relay would resolve the issue for me, but I’m not sure.
Saying that, I thought I had resolved the issue, but I didn’t get an email notification for your reply. I don’t think my SMTP issues are fixed lol.
I would bet if you set a /etc/hosts record for smtp.sendgrid.net that may help within the lemmy app container.
Because Im not using a relay that may be a problem. Frankly i think the app just has a bug. I dont use email much so i just closed registration and called it a day for now. May continue troubleshooting.
You CAN setup a relay though gmail with sasl but i would use a throwaway account if its a big instance.
I changed Kubernetes’ coredns config to forward *.sendgrid.net to 1.1.1.1 rather than my internal Pi-Hole servers, which did seem to help a bit.
Haven’t tried since updating to 0.18.0, so it could be an internal issue as well.