Well, after some experimentation, this is what I found out:
Jenkins takes the email of the committer (not the author). For example, for a commit message that looks like this:
Author: John Smith <author1@example1.com> 2017-07-27 17:15:39 Committer: John Doe <committer1@example2.com> 2017-07-27 17:15:39 Parent: 9c3ff18dda8ca6f7b7ac4ebab4c76d3c85891a33 (commit) Branch: master
Jenkins will take "committer1" and create a completely new user under People with the user ID "committer1" and email "". If this user does not have a password, it will be considered unregistered, so you need to go to the settings for this user and add a password field to it:

So, this is one way to fix the error, but you have to do it for each user, and in a large team it can be tedious.
sashoalm
source share