Context Navigation

Changes between Version 2 and Version 3 of Ticket #28039, comment 1

v2	v3
3	3	In practice, there's a gazillion means to validate an email address — all of them incorrect, btw — and another gazillion means to validate an email message's format and what not. The entire thing is plagued with string encoding bugs and software bugs and what not from one end the other. What ultimately counts for emails is if its recipient will ultimately manage to read it, valid email address and format be damned.
4	4
5		I wanted to stress the above points because if e.g. gmail, hotmail, yahoo, Outlook, OSX Mail, etc. all render the same WP email correctly, then we also need to be pragmatic. For much the same reason that StackOverflow recently fixed its [http://meta.stackexchange.com/q/229431/161742 standards-compliant url encoding], if everyone else accepts WP email formats then methinks this bug should probably be reported upstream to the email client that does not.
	5	I wanted to stress the above points because if e.g. gmail, hotmail, yahoo, Outlook, OSX Mail, etc. all render the same WP email correctly, then we also need to be pragmatic. For much the same reason that StackOverflow recently fixed its [http://meta.stackexchange.com/q/229431/161742 standards-compliant url encoding], if everyone else accepts WP email formats then methinks this bug should probably be reported upstream to the email client that does not — or to PHPMailer, for that matter.
6	6
7	7	Conversely, if hardly anybody accepts them, it's a valid bug that WP should fix.