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

Email address constructed incorrectly even though configured correctly

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • email-ext-plugin
    • None
    • Linux
      Hudson 1.392
      email-ext 1.29

      Given:

      • a user configured with a name containing spaces (i.e. in People > <User> > Your Name) and a valid email address
      • hudson.model.User.get("First name Last name").getProperty(hudson.tasks.Mailer.UserProperty).getAddress() is assigned to an env variable
      • this variable is used by email-ext to send a configured mail

      Then, sending fails because a constructed address is used, containing the name (with spaces).
      When I replace the space with a ".", then it can send the mail, because the address is valid.
      I expect that the configured email address is used instead of a constructed one.

          [JENKINS-8526] Email address constructed incorrectly even though configured correctly

          farshidce added a comment -

          is this feature supported for the built-in email plugin ?
          as far as i remember jenkins expect a comma based list and it doesn't parse string like "John Smit<jsmith@gmail.com>" sort of a string.

          can someone shed some light into this bug ?
          do we need to support the "First Last<email>" for this plugin ?

          farshidce added a comment - is this feature supported for the built-in email plugin ? as far as i remember jenkins expect a comma based list and it doesn't parse string like "John Smit<jsmith@gmail.com>" sort of a string. can someone shed some light into this bug ? do we need to support the "First Last<email>" for this plugin ?

          evernat added a comment -

          It seems to be a duplicate of JENKINS-9160 which is fixed in email-ext v2.15, so resolving as duplicate. Please reopen if not.

          evernat added a comment - It seems to be a duplicate of JENKINS-9160 which is fixed in email-ext v2.15, so resolving as duplicate. Please reopen if not.

            Unassigned Unassigned
            ffouvry ffouvry
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: