The registration process doesn’t validate (bad)email addresses resulting in non_recuperable accounts

    • A_A@lemmy.worldOP
      link
      fedilink
      arrow-up
      8
      ·
      1 year ago

      My concern is more with the involuntary trashing of the namespace : an account registration should be dropped if not validated after a certain amount of time.

        • A_A@lemmy.worldOP
          link
          fedilink
          arrow-up
          4
          ·
          edit-2
          1 year ago

          Please, can someone (lemmyist) with an account on GitHub do this … as I have no knowledge about it 🙏

          Maybe the request for improvement (to be raised on GitHub) could be as such :

          Lemmy account registration should be dropped if not validated after a certain amount of time. Old databases should be revised. To be applied only where an email is required for registration.

          Please be so kind to reply here after you raise it 👍

    • A_A@lemmy.worldOP
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      I did contact him inside this post, now I realize it’s a problem for each and every instances !

  • fubo@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    There really isn’t a reliable way to “validate” email addresses other than to try sending email to them.

    An email address has two parts, separated by the @ sign: the “local part” and the domain. The domain has to follow the rules of DNS, but there are astonishingly few hard rules for the local part.

    A validator can check that the domain resolves — that there’s an A or MX record for it in DNS — but it can’t do much about the part before the @ sign.

    Whether the local part is correct or not depends on the actual behavior of the mail server for the domain; which means that, without actually trying to send email to it, it can’t really be tested.

  • philip@kbin.chat
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    @A_A Thanks for letting me know about the issue. I ran into the same issue with my gmail, but it worked with every other email I had, so thought it was just a one off.
    I will look more into it. See if switching to a different email provider fixes the issue.