-
Bug
-
Resolution: Not A Defect
-
Major
-
None
-
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 "jon@domain1.com". I see a second one as "user1" (which is my unix username) with email address "jon@domain2.com". If I setup a job to send email to "jon@domain1.com" I get the error that the email will not be sent to unregistered users. If I send an email to "jon@domain2.com", 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?
- duplicates
-
JENKINS-9016 Git creates usernames based on 'name' not the email.
-
- Open
-
- is related to
-
JENKINS-43386 Not sending mail to user with permission to view
-
- Open
-
Also having this message
Not sending mail to unregistered user <user-email@domain.com> because your SCM claimed this was associated with a user ID <User Name> which your security realm does not recognize; you may need changes in your SCM plugin
which gives hints that the issue may be with the Security Realm or with the SCM plugin config.
My SCM plugin is Git and I am not seeing any Git setting in Jenkins configuration page that could have any impact on this issue. What should we be looking for ? Where ?
My Security Realm is configured with "Jenkins own user database" and the only option "Allow users to sign up" does not seem to be related to our issue. Am I wrong ? Can the issue lie in the "Authorization" part which in my case is configured as "Project-based Matrix Authorization Strategy" ?
Hence it is not obvious to me how the above message helps figuring out the issue. At this point it looks like it is leading into 2 different false tracks.
So, what it the correct way to interpret this message and what should the one having it really be looking at ?