Status: Closed (View Workflow)
Resolution: Not A Defect
Jenkins Version 2.32.3
Email extension plugin 2.57.1
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 "email@example.com". I see a second one as "user1" (which is my unix username) with email address "firstname.lastname@example.org". If I setup a job to send email to "email@example.com" I get the error that the email will not be sent to unregistered users. If I send an email to "firstname.lastname@example.org", 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?
JENKINS-9016 Git creates usernames based on 'name' not the email.
- is related to
JENKINS-43386 Not sending mail to user with permission to view
Code changed in jenkins
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)
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.
you end up with user accounts for others
They are not real accounts.
this may be a security issue
It is not.
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 email@example.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