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

No email is sent to anyone if there is an invalid email address contained within the email list

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      For some reason the changelog information for a gerrit repo could not be processed properly to provide the revision number, committer name, or anything other than the fact that there was a change.

      These changes get output to the changelog.xml file with nothing but the paths and the committext. When the changelog is processed, the committer name is given as "unknown" with the given domain default.

      Because unknown@mydomain.com is not a valid address, no email is sent out. Even when there are many more valid email addresses to send the notification to.

      I saw where this same type of invalid email address issue was resolved for JENKINS-9006, but we are still experiencing it being rejected with our secured LDAP authentication.

        Attachments

          Activity

          Hide
          slide_o_mix Alex Earl added a comment -

          Please try this one as a test, it should allow HTML emails and have a better log output for invalid addresses.

          Show
          slide_o_mix Alex Earl added a comment - Please try this one as a test, it should allow HTML emails and have a better log output for invalid addresses.
          Hide
          rejesi rejesi added a comment -

          Great - this fix has corrected the email html problem.

          The "unknown@xxx.xxxxxx.com" user is still being sent email even though the log indicates "Error sending to the following INVALID addresses: unknown@xxx.xxxxxx.com" - but this is so much better than no email going out at all.

          The other misleading line in the log has been removed as well.

          Thank you very much for the expedient manner in which you took care of this issue.

          Show
          rejesi rejesi added a comment - Great - this fix has corrected the email html problem. The "unknown@xxx.xxxxxx.com" user is still being sent email even though the log indicates "Error sending to the following INVALID addresses: unknown@xxx.xxxxxx.com" - but this is so much better than no email going out at all. The other misleading line in the log has been removed as well. Thank you very much for the expedient manner in which you took care of this issue.
          Hide
          slide_o_mix Alex Earl added a comment -

          Why do you say the user is still being send the email? Even if it shows up in the "To:" of the email when you receive it, doesn't mean that the email was actually sent to that address. It just means the header of the email lists that user in the To header. There really isn't a way around this.

          Show
          slide_o_mix Alex Earl added a comment - Why do you say the user is still being send the email? Even if it shows up in the "To:" of the email when you receive it, doesn't mean that the email was actually sent to that address. It just means the header of the email lists that user in the To header. There really isn't a way around this.
          Hide
          rejesi rejesi added a comment -

          Hmmm, Just so you know - when valid email addresses and an invalid email address with a bad domain are entered in the "Project Recipient List" to be used as the recipient list for the triggers, it is considered an empty list (per the log message) and no email gets sent to anyone as shown in the log below. There is clearly a red error message on the job config page about the bad domain name - which means that the user just ignored the message.

          Email was triggered for: Success
          Sending email for trigger: Success
          Failed to create e-mail address for sw.int@xxx..xxxxxx.com
          An attempt to send an e-mail to empty list of recipients, ignored.
          Finished: SUCCESS

          The "Project Recipient List" has been used in the trigger emails before if the user wanted the same people to be notified for the respective trigger and didn't put the same names in the respective trigger's "Recipient List"

          But if the bad domain name is in the trigger recipient list it is handled as expected as per the log messages below:

          Email was triggered for: Success
          Sending email for trigger: Success
          Failed to create e-mail address for sw.test@xxx..xxxxxx.com
          Sending email to: sw.int@xxx.xxxxxx.com unknown@xxx.xxxxxx.com
          Successfully sent to the following addresses: sw.int@xxxxxx.com
          Error sending to the following INVALID addresses: unknown@xx.xxxxxx.com
          Finished: SUCCESS

          Show
          rejesi rejesi added a comment - Hmmm, Just so you know - when valid email addresses and an invalid email address with a bad domain are entered in the "Project Recipient List" to be used as the recipient list for the triggers, it is considered an empty list (per the log message) and no email gets sent to anyone as shown in the log below. There is clearly a red error message on the job config page about the bad domain name - which means that the user just ignored the message. Email was triggered for: Success Sending email for trigger: Success Failed to create e-mail address for sw.int@xxx..xxxxxx.com An attempt to send an e-mail to empty list of recipients, ignored. Finished: SUCCESS The "Project Recipient List" has been used in the trigger emails before if the user wanted the same people to be notified for the respective trigger and didn't put the same names in the respective trigger's "Recipient List" But if the bad domain name is in the trigger recipient list it is handled as expected as per the log messages below: Email was triggered for: Success Sending email for trigger: Success Failed to create e-mail address for sw.test@xxx..xxxxxx.com Sending email to: sw.int@xxx.xxxxxx.com unknown@xxx.xxxxxx.com Successfully sent to the following addresses: sw.int@xxxxxx.com Error sending to the following INVALID addresses: unknown@xx.xxxxxx.com Finished: SUCCESS
          Hide
          rejesi rejesi added a comment -

          Sorry, didn't see your remarks. Agreed. I was not implying that it was wrong, as I have no way of knowing what really happens to the email, just that it showed up in the header. And as you indicate, there is no way around it and I am fine with this.

          Show
          rejesi rejesi added a comment - Sorry, didn't see your remarks. Agreed. I was not implying that it was wrong, as I have no way of knowing what really happens to the email, just that it showed up in the header. And as you indicate, there is no way around it and I am fine with this.

            People

            • Assignee:
              slide_o_mix Alex Earl
              Reporter:
              rejesi rejesi
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: