Accounts blackholed when instance email is not working
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?
They def do. I second this @NettoHikari@social.fossware.space would love to see the SQL. I did a basic delete of a couple accounts today using the basic SQL
DELETE FROM local_user WHERE person_id=‘123456’
However I still see some of those users in in the server counts in the sidebar:
In my tshooting today, i dont think it will help. I think the error is hitting in the lemmy app container, and not getting passed to my postfix relay. So even if i say...setup postfix as a dedicated relay (which I have done plenty of), not sure it would help.
I was actually testing email, when I stumbled on this. When i tried another account with the same address I got an error that the address already exists. Prompting me to go cleanup my DB and use something else to test email realy (forgotten passwords in my case).
Something like this happened to me on my badbrainstorm.ml account.
Had an established account from September, hundreds of post. I was attempting to set up 2FA and suddenly I get a notice about not being on version .18
Now it doesn't recognize me as a registered user.
Could someone help me with 2FA, account recovery?
My email is broken since the 0.18 upgrade and its not postfix related that I can tell. The lemmy app/container itself is tossing errors before it ever hits postfix.