Hello Arnt, 

Allow me to explain, while refraining myself who is right or wrong.  

https://eai.xgenplus.com is designed and evolving for users to test their own EMAIL ID for the support of EAI. 

C:- mail from:<xn--11b7am1g.xn--41b5a5av9azf@xn--c2bd1gb.xn—h2brj9c> -  SMTPUTF8 is always added , may be its displayed in next line due to length, please check again. 

The system tries many combinations of FROM to the email address (including punycode)  you submit and tries various combinations and shows how much EAI it supports..

Below is test result of my own EAI address.

aspmx1.spamjadoo.com

EAI SUPPORTED

S:- 220 SpamJadoo Antispam SMTP Service by http://datainfosys.net

C:- ehlo a.tbms.in 

S:- 250-SIZE 26214400

S:- 250-ETRN

S:- 250-SMTPUTF8

S:- 250-8BITMIME

S:- 250-AUTH=LOGIN

S:- 250-AUTH LOGIN PLAIN GSSAPI DIGEST-MD5 CRAM-MD5 NTLM

S:- 250 PIPELINING

C:- mail from:<xn--11b7am1g.xn--41b5a5av9azf@xn--c2bd1gb.xn--h2brj9c> SMTPUTF8 

S:- 250 OK

C:- rcpt to: <अजय@डाटा.भारत> 

S:- 250 OK

C:- rset 

S:- 250 OK

C:- mail from:<=?utf-8?B?4KSm4KWA4KSq4KSVLuCkuOCkv+CkqOCljeCkmOCksg==?=@xn--c2bd1gb.xn--h2brj9c> SMTPUTF8 

S:- 250 OK

C:- rcpt to: <अजय@डाटा.भारत> 

S:- 250 OK

C:- rset 

S:- 250 OK

C:- mail from:<xn--11b7am1g.xn--41b5a5av9azf@डाटा.भारत> SMTPUTF8 

S:- 250 OK

C:- rcpt to: <अजय@डाटा.भारत> 

S:- 250 OK

C:- rset 

S:- 250 OK

C:- mail from:<दीपक.सिन्घल@xn--c2bd1gb.xn--h2brj9c> SMTPUTF8 

S:- 250 OK

C:- rcpt to: <अजय@डाटा.भारत> 

S:- 250 OK

C:- rset 

S:- 250 OK

C:- mail from:<दीपक.सिन्घल@डाटा.भारत> SMTPUTF8 

S:- 250 OK

C:- rcpt to: <अजय@डाटा.भारत> 

S:- 250 OK

C:- rset 

S:- 250 OK

C:- quit 

S:- 221 Ok 

Details:-

punycode@punycode(optional) supported 

ACE@punycode supported 

punycode@unicode(optional) supported 

unicode@punycode supported 

unicode@unicode supported 

 ===============
You will notice SMTPUTF8 is added in every FROM. 

Regarding SPAM , antispam you are using is not ACE aware or considers it bad. 
This is proper ASCII email address xn--11b7am1g.xn--41b5a5av9azf@xn--c2bd1gb.xn—h2brj9c and has punycode into it. Perfectly allowed on for IDN. Remember, its just a test,, In real world scenario from XgenPlus , you will get full UTF8 ID if in From, not the ACE string in envelop. 

Please share your email address with me, i will share the details with you.  Happy to receive suggestions.
 
Thanks.

Dr. Ajay DATA  | Founder & CEO 
Get email id like अजय@डाटा.भारत in your own language,
visit www.xgenplus.com 
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>  MailId : [76777850]
To: Martin J. Drst <duerst@it.aoyama.ac.jp>
Cc: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>,Mark Svancarek <marksv@microsoft.com>,Ajay Data <ajay@data.in>,don.hollander@icann.org,ua-eai@icann.org
Subject: Re: [UA-EAI] EAI Evaluation Widget
Date: 29 Dec 2017 04:52:18 PM

Ayjay’s test isn’t accurate.

SMTP servers mostly reject things because the spam filter says that source does not look like a real mail sender. Ayjay’s test assumes that any rejection is due to a lack of SMTPUTF8 support, whereas real servers block 90-99% of mail due to being spam.

The test also doesn’t behave like a real mail sender so it’s likely to trigger spam filters, too.

Look in particular at this command:

>  C:- mail from:<xn--11b7am1g.xn--41b5a5av9azf@xn--c2bd1gb.xn—h2brj9c>

This command does not test SMTPUTF8 (the word “SMTPUTF8” should have been at the end) and it conditions the server’s spam filter to learn that xn--11b7am1g.xn--41b5a5av9azf@xn--c2bd1gb.xn—h2brj9c is not a real mail sender (quite accurately). If the spam filter classifies mail senders by address, then it’ll learn that there’s nothing to be gained by letting mail from that address through, and it will block the test.

FWIW, my mail setup supports EAI all the way to my phone, and Ayjay’s test is wrong about it too. It says it supports punycode, when in fact none of the three EAI-aware programs do.

Arnt
.

Do not Remove:
[HID]20171229165215738[-HID]