If a student creates a new account and they mis-type (or just plain get wrong) their email address with Email verification turned on there is a problem....
The account gets created but the student gets an error saying that the mail cannot be sent. They are then completely stuck. They cannot log in to the account - it hasn't been verified, and they cannot create a new one without picking a different user name, which at best is inconvenient.
The system should remove the user if the email cannot be sent.
Basically, the student just has to try again and pick a new username.
After 7 days the old, unconfirmed accounts will be automatically deleted by the cron process, and the original username will be freed up again.
I've found it's not quite that bad. The "lost" email goes off into MTA land, wanders about and normally bounces back. I find it actually gets back to the email account specified on the Moodle Admin account (which isn't on the Moodle server but on my desktop). A quick test using a nonexistent Hotmail account had an email bouncing back in less than quarter of an hour. (Maybe Hotmail's good that way ) With about 400 students registered using email verification, I suppose I've gone into the user table about 10 times to delete the "stuck" record. That's nothing to the hassle of pre-registering 400 accounts. Although a GUI to quickly delete an uncomfirmed account would always be welcome - only kidding Martin!
Login as Admin, Edit User Accounts -> sort by Last Access -> goto end of list -> Delete the "Never" user account
Well I never!!
[Not quite sure why it needed to open a new window, but it deleted the unwanted account, perhaps that's a "feature" of the Galeon browser]
I've run into a similar problem: student does everything correctly but carelessly deletes the email with the registration link, then begs for help. Is it possible to have a command which would allow admin to send registration email again, possibly with an option for first changing information such as bad email addresses?