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?

  • tool@r.rosettast0ned.comEnglish
    1·
    1 year ago

    Docker at this depth is a bit new to me. Curious. Why does it need to be bound to the lemmyinternal and lemmyexternalproxy nets, and not just internal?

    Because the “lemmyinternal” network is set as an internal type network in the Docker compose file, which is exactly what it sounds like: internal-only. Postfix wouldn’t have a way to egress to the WAN if not connected to the “lemmyexternal” network, so the initial connection step to send the mail from the “lemmy” container would work, but postfix sending it would fail, as it doesn’t have a route out to the Internet.

    • Freeman@lemmy.pubEnglish
      2·
      1 year ago

      Makes sense. Thanks for the quick explainer (and especially for the tip in the first place.

      Just getting logs in a format I’m used to out of docker had me on a bit of a tangent.