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

Email-ext send email to unknown recipient when email address is not available

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      When email-ext plugin is configured for a build and the build finished, the plugin send email to "unknown" email recipient. The email suffix is globally configured. So probably the email adress for the requester cannot be retrieved. But I think when the email cannot be retrieved the server should not send a email.

      Log:
      Email was triggered for: Success
      Sending email for trigger: Success
      Sending email to: unknown@meine.defaultdomain.com

        Attachments

          Activity

          Hide
          jimjaeger jim jaeger added a comment -

          screenshots attached from project config.

          Show
          jimjaeger jim jaeger added a comment - screenshots attached from project config.
          Hide
          jimjaeger jim jaeger added a comment -

          Some more information about the projects:

          • Maven build
          • RTC Source control
          Show
          jimjaeger jim jaeger added a comment - Some more information about the projects: Maven build RTC Source control
          Hide
          slide_o_mix Alex Earl added a comment -

          When the username isn't a full email address, email-ext will look at the Mailer.UserProperty to get the configured address from Jenkins. This will call the MailAddressResolver resolve method, which goes through all the implemented MailAddressResolvers to find the email address for the user. If one of those is returning "unknown" then that is what email-ext uses. The address resolution is normally implemented in the source control plugin.

          Show
          slide_o_mix Alex Earl added a comment - When the username isn't a full email address, email-ext will look at the Mailer.UserProperty to get the configured address from Jenkins. This will call the MailAddressResolver resolve method, which goes through all the implemented MailAddressResolvers to find the email address for the user. If one of those is returning "unknown" then that is what email-ext uses. The address resolution is normally implemented in the source control plugin.
          Hide
          jimjaeger jim jaeger added a comment -

          The source control plugin is RTC.

          Show
          jimjaeger jim jaeger added a comment - The source control plugin is RTC.
          Hide
          slide_o_mix Alex Earl added a comment -

          Looks like RTC doesn't implement a MailAddressResolver, so something else is returning "unknown" to email-ext. Can you add a logger for hudson.tasks.MailAddressResolver with the level of FINE and it should put info in the log as to what resolver is being used.

          Show
          slide_o_mix Alex Earl added a comment - Looks like RTC doesn't implement a MailAddressResolver, so something else is returning "unknown" to email-ext. Can you add a logger for hudson.tasks.MailAddressResolver with the level of FINE and it should put info in the log as to what resolver is being used.
          Hide
          slide_o_mix Alex Earl added a comment -

          Need more information

          Show
          slide_o_mix Alex Earl added a comment - Need more information

            People

            Assignee:
            slide_o_mix Alex Earl
            Reporter:
            jimjaeger jim jaeger
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: