That email is Joomla's and that should be turned off. Imports in CB work exactly like you created the user manually from backend. This limits what emails it will send. Am reviewing how to best improve this so it behaves more like a frontend user registration depending on if the imported row is confirmed, approved, etc..

forge.joomlapolis.com/issues/8825

Best I can suggest for now is import them then try using "Resend Confirmation" button on their rows. The user import wasn't really meant to be used to bypass registration, but to just move existing users. It definitely needs improvement though and will see if I can have it improved sometime this week.

Ok, have massively redone user import behavior. It now properly handles user state, fallback behaviors, and registration emails. It's possible to import users now with as little information as just an email address and it will fallback everything else. Password is also properly sent in the pending confirmation email during import. A new option is also added to suppress emails for new entries. Your CB configuration also no longer needs to be changed as it'll temporarily override the configuration as needed during import.

Once the changes are reviewed and merged a new build release will be available with these improvements.

This is all fixed in latest CB build release. The import process will now correctly behave like a normal registration.

You no longer need to touch your configuration as it will internally adjust things as needed during the import. If the password is missing it will generate one and if they're unconfirmed it will send pending email with confirmation link.

Normal registration fallback behavior is also implemented so for example if only Name is supplied it will correctly split and store first/middle/last and vise verse. You can now import users with as little information as just a list of email addresses due to fallback behavior now working. The "gids" column isn't required either now as it'll give them default registration usergroup if it's missing now.

For your usage with the latest build release exclude a password column, set confirmed to 0, and block to 1. That should be all you need to adjust. You can actually exclude the block column entirely if you want as it'll adjust based off confirmed and approved state. An example CSV import file is as follows.

name | username | email | confirmed
tom | tom123 | tom@example.com | 0

Super simple imports like that will work as expected. It will create them with that name, username, and email. It'll generate them a password and since they're marked unconfirmed will email them confirmation link. The email will include their generated password as well.

There's also a new dropdown to turn off emails during import for those that need it. This makes it so you don't have to globally turn off emails just to import users.