As long as you don't try to validate the email address I entered. The list of gotchas for email address parsing is impressive too. (e.g. "Cool Address"@example.store is a valid email)
You should validate any email addresses, just keep in mind that proper validation requires you to attempt to send an email to it and check if the user received it.
Not sure why this is getting downvoted. It's a valid point. There is a gap between "technically valid email addresses" and "email addresses that reasonable people use".
3) Realize that undervalidation of input can create opportunities to introduce backdoors into your system.
4) Realize that the added benefit of supporting weird formats are not worth the time to verify that it actually works.
As someone who works on an email client, I can absolutely tell you that using IP address literals and quoted localparts are more trouble than its worth. Chances are, the libraries you use can't handle them anyways. And if you don't try to support quoted localparts, than normalization is a lot easier. (Although I was once locked out of a system because I signed up with an email address that used capitals and the login form changed to lowercase it without changing the database storage, which meant no form I could spell it would cause it to match).
It depends. There are plenty of harmless examples like removing leading/trailing whitespace when entering a name.
Ignoring whitespace, dashes etc. when entering a code, etc.
A bit of extra effort by the developers saves a lot of people a lot of time.
