this post was submitted on 25 Jun 2023
0 points (NaN% liked)

Lemmy Support

4651 readers
1 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 5 years ago
MODERATORS
[email protected]
0
Accounts blackholed when instance email is not working (lemmy.cloudhub.social)
submitted 1 year ago by [email protected] to c/[email protected]
13 comments fedilink hide all child comments
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 0 points 1 year ago* (last edited 1 year ago) (4 children)

It's because the postfix docker container is not connected to a docker network that has access to the "lemmy" or "lemmy-ui" container, it's being connected to the "default" docker network. I submitted a pull request for it here that should fix it.

To make it work in the meantime:

  1. cd into the Lemmy install directory and run docker compose down

  2. Edit docker-compose.yml in the same directory, and in the postfix section, put this just below the postfix: line:

     networks:
   - lemmyinternal
   - lemmyexternalproxy

  3. Run docker compose up -d

The indentation of that code is very important. Your postfix section should look like this when it's done:

postfix indentation

That should connect the "postfix" container in to a docker network that can communicate with the "lemmy" and "lemmy" UI containers. There's another bug in the default config that doesn't assign a hostname to all the containers, but it doesn't always manifest all the time. You can fix that by making sure each service has a hostname assigned to it, like hostname: lemmy, hostname: lemmy-ui, hostname: postfix etc in the respective service's section of the service: section of the docker compose file.

[–] [email protected] 0 points 1 year ago (3 children)

I get an error that the network ‘lemmyinternal’ doesn’t exist when making this change in docker-compose.yml - anything I’m missing?

[–] [email protected] 0 points 1 year ago (2 children)

Make sure the networks section at the top of your docker compose file looks like this:

docker compose networks

[–] [email protected] 1 points 1 year ago (1 children)

Thanks! Somehow missed that in the original post - that worked but I am now seeing “email_not_sent” when trying to test forgot password, how can I get to the postfix log to see what the issue is?

[–] [email protected] 1 points 1 year ago

Make sure the postfix container is connected to the lemmyexternalproxy network.