Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-43759

Not sending email to registered users

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: email-ext-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.46.1
      Email Extension 2.57.2
    • Similar Issues:

      Description

      This may be releated to #43178.

      I have another Jenkins instance that uses the Jenkins internal database. I just upgraded this instance. I have 2 entries on the people page:

      Userid: "Jon Schewe", full name: "Jon Schewe", email "jpschewe@xxx", delete button is active, no password is set. Last commit activity is on my last job.

      Userid: "jpschewe", full name: "Jon Schewe", email "jpschewe@xxx", delete button is NOT active, password is set. Since the password is set, presumably this is who I'm logging in as. There is no last commit activity on this user.

      I committed changes as "jpschewe@xxx" through GitHub. The github hook fired and caused my build to run. At the end of the build:
      19:33:37 Email was triggered for: Always*19:33:37* Sending email for trigger: Always*19:33:37* Not sending mail to unregistered user jpschewe@xxx*19:33:37* An attempt to send an e-mail to empty list of recipients, ignored.
       

      This is using the Jenkins user database, so I would expect this is the case that was tested for, as opposed to my other instance that uses the unix database. This security fix doesn't appear to be working as expected. I understand the concept of not sending emails outside an organization, however the fix that I had before of using a presend script to filter email addresses has worked rather nicely. I'm not sure why Jenkins has 2 users for me in the people list or how this effects this sending of email, but I suspect they are related.

       

        Attachments

          Issue Links

            Activity

            Hide
            davidvanlaatum David van Laatum added a comment -
            Show
            davidvanlaatum David van Laatum added a comment - Daniel Beck
            Hide
            danielbeck Daniel Beck added a comment -

            jpschewe To clarify, this isn't the "mailing list" issue you described in JENKINS-43178?

            David van Laatum I thought I explained somewhere that these users are considered different (Jon describes this in a way I suspect he read my explanation, but it's not in JENKINS-43178). What could be considered here is to search for a legitimate user with the same email address, but that would be an RFE. From my POV this works as intended, even if annoying. If the Git committer's username were 'jpschewe', things would work.

            Show
            danielbeck Daniel Beck added a comment - jpschewe To clarify, this isn't the "mailing list" issue you described in JENKINS-43178 ? David van Laatum I thought I explained somewhere that these users are considered different (Jon describes this in a way I suspect he read my explanation, but it's not in JENKINS-43178 ). What could be considered here is to search for a legitimate user with the same email address, but that would be an RFE. From my POV this works as intended, even if annoying. If the Git committer's username were 'jpschewe', things would work.
            Hide
            jpschewe jpschewe added a comment -

            Daniel Beck This is not the "mailing list" issue. This is a different Jenkins instance using the Jenkins database for access control.

            Show
            jpschewe jpschewe added a comment - Daniel Beck This is not the "mailing list" issue. This is a different Jenkins instance using the Jenkins database for access control.
            Hide
            danielbeck Daniel Beck added a comment -

            Looks superficially like a duplicate of JENKINS-43268 but will need further looking into.

            Show
            danielbeck Daniel Beck added a comment - Looks superficially like a duplicate of JENKINS-43268 but will need further looking into.
            Hide
            jglick Jesse Glick added a comment -

            Very likely an issue in git not email-ext, like JENKINS-9016 perhaps.

            Show
            jglick Jesse Glick added a comment - Very likely an issue in  git not email-ext , like  JENKINS-9016 perhaps.

              People

              • Assignee:
                davidvanlaatum David van Laatum
                Reporter:
                jpschewe jpschewe
              • Votes:
                3 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated: