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

Can't send email to registered users

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: email-ext-plugin
    • Labels:
      None
    • Environment:
      Jenkins Version 2.32.3
      Email extension plugin 2.57.1
    • Similar Issues:

      Description

      I see that some security was added so that emails don't get sent to people that shouldn't get emails. I had fixed this by using a pre-send script that filtered out email addresses. However now with the new change, emails are not getting sent at all. I use the unix database backend for my Jenkins system. If I goto the People page I see 2 entries for myself, one as "Jon Schewe" with an email address "jon@domain1.com". I see a second one as "user1" (which is my unix username) with email address "jon@domain2.com". If I setup a job to send email to "jon@domain1.com" I get the error that the email will not be sent to unregistered users. If I send an email to "jon@domain2.com", then it works. Note that I've set "domain2.com" as my default email suffix.

       

      So the first question here is what is a registered user when using the unix database backend?

      Second, what is considered the email address for a registered user when using the unix database backend?

       

        Attachments

          Issue Links

            Activity

            Hide
            aflat aflat added a comment -

            I have hit the same issue with ldap backed git server, and ldap backed jenkins. This looks like a git scm issue, as it's getting a username of first.last from the email address first.last@actifio.com. Yet my users have a username of firstlast.

            It looks like svn may have the same issue. Sadly it crops up in this plugin as a bug.

            I have added a pull request to add a checkbox to the global config to allow unregistered emails to be sent, so you don't have to set the prop on the jenkins statup command line

            Show
            aflat aflat added a comment - I have hit the same issue with ldap backed git server, and ldap backed jenkins. This looks like a git scm issue, as it's getting a username of first.last from the email address first.last@actifio.com. Yet my users have a username of firstlast. It looks like svn may have the same issue. Sadly it crops up in this plugin as a bug. I have added a pull request to add a checkbox to the global config to allow unregistered emails to be sent, so you don't have to set the prop on the jenkins statup command line
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: George
            Path:
            src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java
            src/main/java/hudson/plugins/emailext/plugins/recipients/RecipientProviderUtilities.java
            src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/global.groovy
            src/main/webapp/help/globalConfig/allowUnregistered.html
            http://jenkins-ci.org/commit/email-ext-plugin/19081b2aa3d32c479125b538c545fdd3065960f8
            Log:
            JENKINS-43268 adding global checkbox to allow sending to unregistered emails. This is a workaround to a SCM plugin issue, like JENKINS-9016 and probably others (#161)

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: George Path: src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java src/main/java/hudson/plugins/emailext/plugins/recipients/RecipientProviderUtilities.java src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/global.groovy src/main/webapp/help/globalConfig/allowUnregistered.html http://jenkins-ci.org/commit/email-ext-plugin/19081b2aa3d32c479125b538c545fdd3065960f8 Log: JENKINS-43268 adding global checkbox to allow sending to unregistered emails. This is a workaround to a SCM plugin issue, like JENKINS-9016 and probably others (#161)
            Hide
            jpschewe jpschewe added a comment -

            I have found that the git SCM plugin now allows me to automatically create users for authors in commits. Enabling this appears to have fixed most issues with emailing users. It does have the downside that you end up with user accounts for others and this may be a security issue.

            Show
            jpschewe jpschewe added a comment - I have found that the git SCM plugin now allows me to automatically create users for authors in commits. Enabling this appears to have fixed most issues with emailing users. It does have the downside that you end up with user accounts for others and this may be a security issue.
            Hide
            jglick Jesse Glick added a comment -

            you end up with user accounts for others

            They are not real accounts.

            this may be a security issue

            It is not.

            Show
            jglick Jesse Glick added a comment - you end up with user accounts for others They are not real accounts. this may be a security issue It is not.
            Hide
            jpschewe jpschewe added a comment -

            That's excellent news! I feel much more comfortable enabling this other places then.

            Show
            jpschewe jpschewe added a comment - That's excellent news! I feel much more comfortable enabling this other places then.

              People

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

                Dates

                • Created:
                  Updated: