<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:Mangal;
panose-1:0 0 4 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:"Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:windowtext">I still feel this is too complex for the average web developer. I would just look for <anytext> + @ + <anytext>, and send a test email. Looking for dots in the domain part requires you to understand which
is the domain part, which requires you to understand bidi rules.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">Sending a test email pushes the complexity to your email program, of course, and non-UA behavior in the email ecosystem remains. But it’s easier for UASG to measure and inform the relatively small set of
email ecosystem players than it is to inform every website developer that uses regexes, let alone to influence them to consistently change.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">Does that make sense?<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="color:windowtext"><o:p> </o:p></span></a></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:windowtext">From:</span></b><span style="color:windowtext"> ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org]
<b>On Behalf Of </b>Asmus Freytag<br>
<b>Sent:</b> Wednesday, September 13, 2017 3:17 PM<br>
<b>To:</b> ua-discuss@icann.org<br>
<b>Subject:</b> Re: [UA-discuss] Re : Re: Regular Expression<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 9/13/2017 10:32 AM, Dr. AJAY D A T A wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">This is what Microsoft suggests for EAI Validation.<br>
<br>
<a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fblogs.msdn.microsoft.com%2Fshawnste%2F2014%2F04%2F01%2Feai-email-address-internationalization-address-validation%2F&data=02%7C01%7Cmarksv%40microsoft.com%7Cb542ae9cd6564c12531208d4faf5266a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636409378204623021&sdata=TbjHDjr1MUow%2Bj2z392Eh4V3RPZMTvoKApAakK55e1s%3D&reserved=0">https://blogs.msdn.microsoft.com/shawnste/2014/04/01/eai-email-address-internationalization-address-validation/</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</blockquote>
<p class="MsoNormal">"^([a-zA-Z0-9.!#$%&'*+/=?^_`{|}~\u00A0-\uD7FF\uE000-\uFFFF-]|([\uD800-\uDBFF][\uDC00\uDFFF]))+$"<br>
<br>
This would allow most of the ASCII range and all of UTF-16 beyond ASCII.<br>
<br>
It would have been cleaner/clearer to express the reverse, that is, all code points not allowed, such as {@, ", controls, Space, NBSP, etc).<br>
<br>
The blog post suggests splitting the address at the @ and separately using the validation regex on the localpart and translation to punycode for the host (using a validating converter).<br>
<br>
A./<br>
<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div id="mySignature">
<div>
<div>
<div>
<p class="MsoNormal"><strong><span style="font-size:8.5pt;font-family:"Tahoma",sans-serif;color:#333399">Dr. Ajay DATA</span></strong><span style="font-size:8.5pt;font-family:"Tahoma",sans-serif;color:#333399">
<strong><span style="font-family:"Tahoma",sans-serif"> | Founder & CEO </span></strong></span><span style="font-size:13.5pt"><o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt">Get email id like </span><strong><span lang="HI" style="font-size:7.5pt;font-family:"Mangal",serif"><a href="mailto:अजय@डाटा.भारत"><span style="font-weight:normal">अजय</span><span lang="EN-US" style="font-family:"Calibri",sans-serif;font-weight:normal">@</span><span style="font-weight:normal">डाटा.भारत</span></a></span></strong><span style="font-size:10.0pt"> in
your own language,<br>
visit <a href="https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.xgenplus.com%2F&data=02%7C01%7Cmarksv%40microsoft.com%7Cb542ae9cd6564c12531208d4faf5266a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636409378204623021&sdata=3zd14Z8%2FLa0hJEERX6i6TRTIB5hM6FynLBu8Tz7EKYY%3D&reserved=0" target="_blank"><span style="font-size:7.5pt">www.xgenplus.com</span></a> </span><span style="font-size:13.5pt"><o:p></o:p></span></p>
</div>
</div>
<div id="__hggasdgjhsagd_once">
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<p class="MsoNormal"><strong><span style="font-family:"Calibri",sans-serif">From:</span></strong> Don Hollander
<a href="mailto:don.hollander@icann.org"><don.hollander@icann.org></a> <span style="font-size:7.5pt;font-family:"Verdana",sans-serif">MailId : [73397993]</span><br>
<strong><span style="font-family:"Calibri",sans-serif">To:</span></strong> Mark Svancarek
<a href="mailto:marksv@microsoft.com"><marksv@microsoft.com></a><br>
<strong><span style="font-family:"Calibri",sans-serif">Cc:</span></strong> Universal Acceptance
<a href="mailto:ua-discuss@icann.org"><ua-discuss@icann.org></a><br>
<strong><span style="font-family:"Calibri",sans-serif">Subject: </span></strong>Re: [UA-discuss] Regular Expression<br>
<strong><span style="font-family:"Calibri",sans-serif">Date:</span></strong> 13 Sep 2017 10:37:07 PM
<br>
<br>
Mark.<br>
<br>
What would such a RegEx look like?<br>
<br>
D<br>
<br>
> On 14/09/2017, at 4:26 AM, Mark Svancarek via UA-discuss <a href="mailto:ua-discuss@icann.org">
<ua-discuss@icann.org></a> wrote:<br>
> <br>
> Depending on your mail client, you may have experienced a linkification error in my response. Weird.
<br>
> <br>
> -----Original Message-----<br>
> From: Mark Svancarek <br>
> Sent: Wednesday, September 13, 2017 9:21 AM<br>
> To: `Vittorio Bertola` <a href="mailto:vittorio.bertola@open-xchange.com"><vittorio.bertola@open-xchange.com></a>; Chaals McCathie Nevile
<a href="mailto:chaals@yandex.ru"><chaals@yandex.ru></a>; <a href="mailto:ua-discuss@icann.org">
ua-discuss@icann.org</a><br>
> Subject: RE: [UA-discuss] Regular Expression<br>
> <br>
> I believe that validation should be as light as possible. "Contains `@` " is about the extent of it unless you are willing to look at bidi and IFS. Just capture the string and send a test message.<br>
> <br>
> -----Original Message-----<br>
> From: <a href="mailto:ua-discuss-bounces@icann.org">ua-discuss-bounces@icann.org</a> [<a href="mailto:ua-discuss-bounces@icann.org">mailto:ua-discuss-bounces@icann.org</a>] On Behalf Of Vittorio Bertola<br>
> Sent: Wednesday, September 13, 2017 1:34 AM<br>
> To: Chaals McCathie Nevile <a href="mailto:chaals@yandex.ru"><chaals@yandex.ru></a>;
<a href="mailto:ua-discuss@icann.org">ua-discuss@icann.org</a><br>
> Subject: Re: [UA-discuss] Regular Expression<br>
> <br>
>> Il 13 settembre 2017 alle 0.01 Chaals McCathie Nevile <a href="mailto:chaals@yandex.ru">
<chaals@yandex.ru></a> ha scritto:<br>
>> <br>
>> <br>
>> On Tue, 12 Sep 2017 22:43:09 +0200, Don Hollander <br>
>> <a href="mailto:don.hollander@icann.org"><don.hollander@icann.org></a> wrote:<br>
>> <br>
>> I think there is value in validation - first, to determine whether an <br>
>> email address is real - if it isn`t, you are probably better off <br>
>> getting a warning than trying to send it.<br>
> <br>
> But this is nothing you can do just with a regexp. The regexp could allow you to intercept blatant mistakes - e.g., there are national keyboards where typing "@" requires pressing Alt or some uncommon combination of keys, so it`s easy to mistype it and you
can easily warn the user that their entered string does not have a "@" - but anything beyond that is unnecessary, because, if a user mistypes an email address in any other way, it`s very likely that he will still end up entering a valid email address that
no regexp will be able to tell as non-existing, or that could even exist but belong to someone else.<br>
> <br>
> On the other hand, if you try to implement a complex regexp, and especially if you try to figure it out on your own, it`s almost certain that you will mark as invalid several valid email addresses that are corner cases but should be accepted, as well as
many future developments of the standards which are invalid now but will be valid in the future.<br>
> <br>
>> Second, I find it very helpful, including as a protection against <br>
>> phishing emails, to be told if an email is not recognised as a contact <br>
>> to whom I have *sent* an email, which is a stricter validation check.<br>
>> Applications that do that for me - especially for scripts I don`t read <br>
>> fluently like Chinese - are common, and I would be upset if they were to stop validating.<br>
> <br>
> But this, again, is a validation that cannot be done via a regexp (can you write a regexp representing your entire contact book?) and that, on the other hand, poses an additional stricter condition than just "the email address is valid". We are just discussing
how to check that the email address is syntactically valid, any other checks could still be implemented however appropriate.<br>
> <br>
> The point here is that you should not try to determine whether an email address is valid by checking its syntax, other than checking that it has a "@" and possibly a "." on the right of it (but even this latter condition is already too strict, as the ideographic
full stop "<span lang="JA" style="font-family:"MS Gothic"">。</span>" should be accepted in place of the ASCII dot, if you check strings in IDN form). Anything beyond that is going to exclude some valid addresses while not increasing in any significant way
your chances of intercepting user input error at this stage - and you will still intercept any user error a few seconds later, when you send the validation/confirmation message.<br>
> <br>
> Regards,<br>
> -- <br>
> <br>
> Vittorio Bertola | Research & Innovation Engineer <a href="mailto:vittorio.bertola@open-xchange.com">
vittorio.bertola@open-xchange.com</a> Open-Xchange Srl - Office @ Via Treviso 12, 10144 Torino, Italy<br>
<br>
Don Hollander<br>
Universal Acceptance Steering Group<br>
Skype: don_hollander<br>
<br>
<br>
<br>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:white">Do not Remove:<br>
[HID]20170913223703930[-HID]</span><img border="0" id="_x0000_i1026" src="https://data.in/XGenPlusMessageID:15053239640295291a-#RCPT#.jpg">
<img border="0" id="_x0000_i1027" src="http://dlr.tbms.in:8077/XET9956:201709.jpg"><o:p></o:p></p>
</blockquote>
<p><o:p> </o:p></p>
</div>
</body>
</html>