+1 on the regexp validation, there is no way to validate an email is correct with a regexp anyway. I would suggest simply validating the field is not blank... for the rest there is a test feature to validate we can send an email to the specified adress.

Or just check that the string contains one (and only one) "@" and at least a "." ? 

I think the regexp was added to avoid misprints and a bit the server injections.

The server is itself protected thus the regexp is probably useless.

jm_meessen there's no requirement for a '.', an @ is the only thing you can check for and what's the point then in this case.

the way to validate an email is to send a user an email and get a code from them...

I agree with you timja

The real fix should be to have a 2 steps validation with a code sent by email that you should pass to validate the ownership (to avoid SPAM and misconfigurations)

to be honest, the main challenge for me is not the server part but doing such UI in Jenkins which doesn't provide a too bad UX