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

“Unregistered user” warning skipping addresses under inappropriate conditions

    XMLWordPrintable

Details

    Description

      Security patch broke it. If configured email is not attached to a know user fails to send email with

       Not sending mail to unregistered user xxx@example.com

       turns out it wasn't what I thought but keeping open as so many people have added similar issues

      Attachments

        Issue Links

          Activity

            Just released a new version that gives a more detailed message that may help identify the problem (configuration or code)

            davidvanlaatum David van Laatum added a comment - Just released a new version that gives a more detailed message that may help identify the problem (configuration or code)

            Which version ?

            What message ?

            valentin92 Valentin Chartier added a comment - Which version ? What message ?
            rqueue Ron Quintos added a comment -

            Currently have 2.60.2 and this is still active. My configuration is similar to danielmish. I have a subversion configuration with active directory in use. The email it complains about is a valid email. Seems that a user is created based on a committer in svn, but that is considered the unregistered user.

            rqueue Ron Quintos added a comment - Currently have 2.60.2 and this is still active. My configuration is similar to danielmish . I have a subversion configuration with active directory in use. The email it complains about is a valid email. Seems that a user is created based on a committer in svn, but that is considered the unregistered user.
            danielbeck Daniel Beck added a comment -

            Right, this issue is SCM-specific. In the case of Subversion, https://github.com/jenkinsci/subversion-plugin/blob/8ef22113a307da105a5d54d7db7ce7b56af85818/src/main/java/hudson/scm/SubversionChangeLogSet.java#L307 is probably too simple – it should try to do more to look up the actual account inside Jenkins.

            FWIW if both SVN and Jenkins are backed by the same LDAP, it can work nicely. The problem occurs on mismatch.

            danielbeck Daniel Beck added a comment - Right, this issue is SCM-specific. In the case of Subversion, https://github.com/jenkinsci/subversion-plugin/blob/8ef22113a307da105a5d54d7db7ce7b56af85818/src/main/java/hudson/scm/SubversionChangeLogSet.java#L307 is probably too simple – it should try to do more to look up the actual account inside Jenkins. FWIW if both SVN and Jenkins are backed by the same LDAP, it can work nicely. The problem occurs on mismatch.

            danielbeck Just thinking about the mapping thing I think the best solution for this is to add a generic way for users to associate SCM details with their user account that each SCM can extend as required. This would allow users to tell jenkins I am known by this username on all SVN repositories matching this server name/pattern. For git attaching multiple email addresses to an account is probably sufficient. 

            davidvanlaatum David van Laatum added a comment - danielbeck Just thinking about the mapping thing I think the best solution for this is to add a generic way for users to associate SCM details with their user account that each SCM can extend as required. This would allow users to tell jenkins I am known by this username on all SVN repositories matching this server name/pattern. For git attaching multiple email addresses to an account is probably sufficient. 

            People

              Unassigned Unassigned
              davidvanlaatum David van Laatum
              Votes:
              33 Vote for this issue
              Watchers:
              40 Start watching this issue

              Dates

                Created:
                Updated: