<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 9/13/2017 10:32 AM, Dr. AJAY D A T A
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:874585640.490311505323969166.JavaMail.root@mx2.datainfosys.com">
<div>This is what Microsoft suggests for EAI Validation.<br>
<br>
<a class="moz-txt-link-freetext" href="https://blogs.msdn.microsoft.com/shawnste/2014/04/01/eai-email-address-internationalization-address-validation/">https://blogs.msdn.microsoft.com/shawnste/2014/04/01/eai-email-address-internationalization-address-validation/</a></div>
<div> </div>
</blockquote>
"^([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>
<blockquote type="cite"
cite="mid:874585640.490311505323969166.JavaMail.root@mx2.datainfosys.com">
<div> </div>
<div> </div>
<div id="mySignature">
<div>
<div style="font-weight: normal; font-size: medium;">
<div><span style="color: #333399; font-family: Tahoma;
font-size: 11px;" data-mce-mark="1"><strong>Dr. Ajay <span
style="color: #333399; font-family: Tahoma;
font-size: 11px;" data-mce-mark="1">DATA</span></strong>
<strong><span style="color: #333399; font-family:
Tahoma; font-size: 11px;" data-mce-mark="1"> </span>|
Founder & CEO </strong></span></div>
</div>
<div style="font-weight: normal; font-size: medium;"><span
style="font-size: x-small;">Get email id like <strong
style="font-size: 10px;">अजय@डाटा.भारत</strong> in your
own language,<br>
visit <a style="font-size: 10px;"
href="http://www.xgenplus.com/" target="_blank"
moz-do-not-send="true">www.xgenplus.com</a> </span></div>
</div>
<div id="__hggasdgjhsagd_once" style="display: none;"> </div>
</div>
<hr><strong>From:</strong> Don Hollander
<a class="moz-txt-link-rfc2396E" href="mailto:don.hollander@icann.org"><don.hollander@icann.org></a> <span style="font-family:
verdana; font-size: xx-small;">MailId : [73397993]</span><br>
<strong>To:</strong> Mark Svancarek <a class="moz-txt-link-rfc2396E" href="mailto:marksv@microsoft.com"><marksv@microsoft.com></a><br>
<strong>Cc:</strong> Universal Acceptance
<a class="moz-txt-link-rfc2396E" href="mailto:ua-discuss@icann.org"><ua-discuss@icann.org></a><br>
<strong>Subject: </strong>Re: [UA-discuss] Regular Expression<br>
<strong>Date:</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 class="moz-txt-link-rfc2396E" 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 class="moz-txt-link-rfc2396E" href="mailto:vittorio.bertola@open-xchange.com"><vittorio.bertola@open-xchange.com></a>; Chaals McCathie Nevile
<a class="moz-txt-link-rfc2396E" href="mailto:chaals@yandex.ru"><chaals@yandex.ru></a>; <a class="moz-txt-link-abbreviated" 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 class="moz-txt-link-abbreviated" href="mailto:ua-discuss-bounces@icann.org">ua-discuss-bounces@icann.org</a>
[<a class="moz-txt-link-freetext" 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 class="moz-txt-link-rfc2396E" href="mailto:chaals@yandex.ru"><chaals@yandex.ru></a>;
<a class="moz-txt-link-abbreviated" 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 class="moz-txt-link-rfc2396E" 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 class="moz-txt-link-rfc2396E" 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 "。" 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 class="moz-txt-link-abbreviated" 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="color: #ffffff; font-family: arial; font-size:
xx-small;">Do not Remove:<br>
[HID]20170913223703930[-HID]</span><img
src="https://data.in/XGenPlusMessageID:15053239640295291a-#RCPT#.jpg"
moz-do-not-send="true" height="1px" width="1px">
<img src="http://dlr.tbms.in:8077/XET9956:201709.jpg"
moz-do-not-send="true" height="1px" width="1px">
</blockquote>
<p><br>
</p>
</body>
</html>