[drgrice1]

Add an isValidEmailAddress method to WeBWorK::Utils that uses Email::Address::XS to check that an email address is valid, and use it wherever a user's email address is set (other than from an LMS via LTI).

• Account Settings page: An invalid new address is rejected with a message.
• Classlist editor: An invalid address is rejected with a message and the user's address is left unchanged. An empty address is still allowed.
• Classlist import (both from the classlist editor and the importClassList.pl and addcourse scripts): An invalid address is replaced with an empty address and the user is still imported, and the affected users are reported.
• Add Users page: A user with an invalid address is not added and the reason is shown in the report.
• Course Administration add course form: An invalid address for an additional user is a validation error.
• Course actions API addUser method: Adding a new user with an invalid address returns an error.
• Feedback page: The sender's address is validated with the same method instead of a custom regular expression.

[pstaabp]

This looks like it is detecting bad emails everywhere they can be entered.

I was testing in the Add users section of the Accounts Manager and putting it a bad email address gives the message but clears all of the input. I realize this is a the same behavior as before but could we instead keep the previous input in each box and perhaps put a red outline around the email box--this could be done for the login name as well.

[pstaabp]

👍