Status: Open (View Workflow)
Jenkins LTS 2.46.1, EmailExtPlugin 2.57.1, role based matrix used
After the latest update with the security patch, no mails sended anymore to "requester" of a job.
The error message in job console looks like this:
Not sending mail to user email@example.com with no permission to view currentJob
When setting the suggested property
The user has overall read permission (matrix based security setup) and for the conrete job the permission:
The user has an account (if I click on the user which started the job .. also belongs to this job (can seen in the user view)) and the mail address is correct.
What permissions or settings are required to avoid this problem? We do not like to have this system property enabled.
Thanks for the great plugin and support!
JENKINS-9016 Git creates usernames based on 'name' not the email.
- is blocked by
JENKINS-46292 Issue when sending emails to Developers
- is duplicated by
JENKINS-46292 Issue when sending emails to Developers
- is related to
JENKINS-43268 Can't send email to registered users
same issue here, We use the Github OAuth Plugin
Very likely an issue in git not email-ext, like JENKINS-9016 perhaps.
Issue reproduced here, also using Github OAuth Plugin.
It seems it is not really related to the email-ext plugin, since it happens with the mailer plugin too.
Fixed the task summary which suggested that the user without read permission is denied access, whereas the user does have the permission and is denied anyway.
We recently updated from a quite old version (1.6 ish) and this is now happening to us too. We have users with employee numbers and then also vanity e-mails. In the logs, it complains that the vanity e-mails do not have permission to view job. I have tried to artificially give "them" permission and so far no luck. This is using the Roles Based permissions (which seems to work fine) except that only some e-mails are going out.
catonyx That suggests that the email attached to the jenkins user is not the email it's trying to send to, they must match or it will put them into the no access category. And by jenkins user I mean the one they login to not the fake users you see under the people link that it creates for each seen committer
davidvanlaatum You are right and that is what is in most logs/consoles. Not sure if I can force this or not. We login with our employee number which is a LDAP server, I think. In our CM tool, we have firstname.lastname@example.org. So, then Jenkins seems to find both the CM variation and the number @ company.com. I tried editing some of the "people" to use the other e-mail and so far no luck.
Not sure if it will just get undone again but users can try login to jenkins clicking their name up in the top right then configure on the left and changing their email
After many unsuccessful tries to give "unknown" users read access, I found this is the only way which essentially disables the security. In particular, I used the second one below and e-mail notification seem to be back to our normal. Bummer there isn't a better way. Also, it seems I only needed to do this on the master (which after digging, I found that modifying the jenkins.xml was the easiest way).
If the security fix is undesirable in a particular instance, it can be disabled with either or both of the following two system properties:
- -Dhudson.tasks.MailSender.SEND_TO_UNKNOWN_USERS=true: send mail to build culprits even if they do not seem to be associated with a valid Jenkins login.
- -Dhudson.tasks.MailSender.SEND_TO_USERS_WITHOUT_READ=true: send mail to build culprits associated with a valid Jenkins login even if they would not otherwise have read access to the job.
We've run into this too. We're using the " Github Authentication Plugin" and the "GitHub Committer Authorization Strategy". I noticed it appears that email addresses owned by admins (as defined by users listed in the GitHub Authorization Settings->Admin User Names field) are not filtered out. Non-admin jenkins user's email addresses are filtered out with the "Not sending mail to user email@example.com with no permission to view" message.
So this leads me to hypothesize there's a bug in either the github plugin, or how it is used by other components for authorization decisions.
Just updated my Gitlab Oauth settings with a Group name for all users. Works as expected, only authorised users who belong to the group set on Gitlab can log in to Jenkins
Unfortunately I also now get the messages
Not sending mail to user <username@...> with no permission to view <Jenkins Jobname>
If I set Global Security->Gitlab OAuth Settings -> Authenticated Users to allow View Read it works ok.
if I set the same using the Group Name ist does not work.
I would rate this as a more serious bug - I will try the workaround mentioned above ( SEND_TO_USERS_WIITHOUT_READ ) - it is a workaround.
( I also had to set SEND_TO_UNKNOWN_USERS a long time ago... - also a bug, users are known)
Jenkins Version 2.176 ( just about to go to 2.177)
Email Extension plugin - 2.66
Gitlab OAuth 1.4
Experiencing similar issues as sgjenkins. Using github oauth client for a github organization and can't get email to send. I've tried checking "Allow sending to unregistered users" with no change. I still get:
"Not sending mail to user firstname.lastname@example.org with no permission to view My Project » my-branch#40An attempt to send an e-mail to empty list of recipients, ignored."
in this area i am seeing something like this (with some obfuscation):
Warning: email@example.com is not a recognized user, but sending mail anyway
Not sending mail to user firstname.lastname@example.org with no permission to view PROJECT_repo » task/master/branch_name #3Warning: email@example.com is not a recognized user, but sending mail anyway
Sending email to: firstname.lastname@example.org email@example.com
I feel like there should be a line break between "#3" and "Warning".
used platform is: Jenkins 2.235.5
For what it's worth, I am seeing this same issue after I turned on the Bitbucket OAuth Plugin and enabling the Authorization Matrix. So I think it's based on the AuthZ matrix and not necessarily the OAuth plugin in use (as it seems that people are seeing this with Github, Gitlab, and Bitbucket OAuth).
I do NOT have the 'allow any authenticated user read access' because it appears any user with a valid BB account can authenticate, even if they are not a member of my group.
I'm on Jenkins 2.319.2
seems this issue is a bit related to
JENKINS-43268.. but also different in error message and setup