FusionAuth
    • Home
    • Categories
    • Recent
    • Popular
    • Pricing
    • Contact us
    • Docs
    • Login

    Verification email is not sent to the specific user

    Scheduled Pinned Locked Moved
    Q&A
    2
    5
    1.1k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • I
      ishuvalov
      last edited by

      The tenant's SMTP setting are correct and test emails are successfully delivered. I'm evaluating the FusionAuth right now and often delete/re-create users with the same emails. Verification emails are delivered to all users but one. The only thing that distinguishes the problem user from the others is the fact I initially registered him via Facebook identity provider, so his email was automatically verified. After that I deleted the user and trying to register it with just an email (not Facebook). And emails are not delivered. Manually sent SMTP test emails to that address also delivered successfully.

      1 Reply Last reply Reply Quote 0
      • danD
        dan
        last edited by

        Hmmm.

        Did you delete the user via the API? Was it a soft delete or a hard delete? I'm just wondering if the user was completely gone or if there was some data left around.

        Is there any other difference between the users which receive the verification emails and the one who does not, or is the FB setup the only difference?

        --
        FusionAuth - Auth for devs, built by devs.
        https://fusionauth.io

        1 Reply Last reply Reply Quote 0
        • I
          ishuvalov
          last edited by

          I deleted all users via admin GUI. I'm not sure what is hard or soft delete. I have entered the DELETE word to confirm the deletion.
          Yes, the only difference is the initial registration via Facebook.
          On the Source tab in the raw data for the user it has {verified: false}, but in the registration data it shows as verified {registrations: [{applicationId: '...', verified: true}]}
          Like If the registration has been cached between user deletion/creation attempts. I hope it helps.

          1 Reply Last reply Reply Quote 0
          • danD
            dan
            last edited by

            OK, sounds like a possible bug to me. Can you please file (with recreation steps) here: https://github.com/FusionAuth/fusionauth-issues/issues/new?template=bug_report.md

            Thanks!

            --
            FusionAuth - Auth for devs, built by devs.
            https://fusionauth.io

            1 Reply Last reply Reply Quote 0
            • danD
              dan
              last edited by

              For anyone else, the bug filed is here: https://github.com/FusionAuth/fusionauth-issues/issues/941

              --
              FusionAuth - Auth for devs, built by devs.
              https://fusionauth.io

              1 Reply Last reply Reply Quote 0
              • First post
                Last post