Do you (ie OpenXchange) or someone else within the EAI group have a set of tests that should be run and the expected results?

I haven't seen one. There's rather a wide range of places to test, like internal operations about whether it does the right thing when you send an EAI message into a mail system, whether it still does the right thing if you remail it back out, and separately whether the MUA (or the UA part of webmail) shows addresses correctly in message headers and address books. You probably want to separate out the back end tests from UA tests since other than webmail they're different unrelated software, e.g. postfix and dovecot on the back, Outlook or Thunderbird on the front. R's, John

From ascii@idn.idn<mailto:ascii@idn.idn> To ascii@ascii.ascii<mailto:ascii@ascii.ascii> hosted by an EAI Ready mail system Name displays properly

OK.

To ascii@ascii.ascii<mailto:ascii@ascii.ascii> hosted by a non-EAI ready mail system Something else?

That should reject the message altogether.

Thanks you Abdalmonem. The list below was just a sample I don’t think building a test plan will be difficult, but it will be effortful. I am hoping that someone has a complete test plan that they are willing to share. From: Abdalmonem Tharwat Galila [mailto:agalila@mcit.gov.eg] Sent: Thursday, 15 February 2018 9:11 PM To: Don Hollander <don.hollander@icann.org>; Michael Slusarz <michael.slusarz@open-xchange.com>; ua-eai@icann.org Subject: [Ext] RE: [UA-EAI] EAI Example Messages Don , kindly find my below reply highlighted with Yellow. Thnx All the Best, Abdalmonem Tharwat Galila Deputy Manager, Dot Masr Registry, Operation Sector. [NTRA Logo 2016] National Telecommunication Regulatory Authority [Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: 1365523405_telephone] Office Tel.: +2 02 35341582 - +2 02 35341300 [Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Mobile] Mobile: +2 010 00049068 [Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: ICON] Fax : +2 02 35370537 [Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: oNLINE] Website : http:\\www.mcit.gov.eg[mcit.gov.eg]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.mcit.gov.eg_&d=DwMGa...> : http:\\www.tra.gov.eg[mcit.gov.eg]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.mcit.gov.eg_&d=DwMGa...> [Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: 1365523294_email] E-mail : agalila@mcit.gov.eg<mailto:agalila@mcit.gov.eg> : atharwat@tra.gov.eg<mailto:atharwat@tra.gov.eg> [Description: 1447802547_skype] Skype : abdalmonem.galila [Description: static_qr_code_without_logo] [Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: 1365523469_error]DISCLAIMER This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please notify your system support manager. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the National Telecom Regulatory Authority (NTRA) . Finally, the recipient should check this email and any attachments for the presence of viruses. The NTRA accepts no liability for any damage caused by any virus transmitted by this email. From: UA-EAI [mailto:ua-eai-bounces@icann.org] On Behalf Of Don Hollander Sent: Wednesday, February 14, 2018 10:10 PM To: Michael Slusarz <michael.slusarz@open-xchange.com<mailto:michael.slusarz@open-xchange.com>>; ua-eai@icann.org<mailto:ua-eai@icann.org> Subject: Re: [UA-EAI] EAI Example Messages Michael: Thanks for building this. Do you (ie OpenXchange) or someone else within the EAI group have a set of tests that should be run and the expected results? For example: From ascii@idn.idn<mailto:ascii@idn.idn> To ascii@ascii.ascii<mailto:ascii@ascii.ascii> hosted by an EAI Ready mail system Message will be received by the recipient and displayed correctly To ascii@ascii.ascii<mailto:ascii@ascii.ascii> hosted by a non-EAI ready mail system At some mail servers , it will be rejected completely “ex. ICANN mail server”. Other mail servers, message received and some mail clients will display domain name or mailbox name correctly. Expected results: Name displays properly Something else? Could mail client reply to this EAI address !!! as I face an issue with my IOS mail clinet. As I talk to people about performing the EAI Evaluation that are concerned that we’ve not provided a sufficiently detailed scope of the work. And based on the results from the recent linkification review, I think that’s fair enough. I’m hoping that someone has a pretty standard test suite and criteria that they’ve been using and are happy to share. Don From: ua-eai-bounces@icann.org<mailto:ua-eai-bounces@icann.org> [mailto:ua-eai-bounces@icann.org] On Behalf Of Michael Slusarz Sent: Friday, 2 June 2017 7:54 AM To: ua-eai@icann.org<mailto:ua-eai@icann.org> Subject: [UA-EAI] EAI Example Messages Hi All, As promised during the Redmond meeting, I have completed the initial pass at creating a corpus of example messages containing data pertinent to implementation of EAI. The initial messages are nothing more than taking the example EAI e-mail addresses listed in UASG004 and inserting them into RFC 5322 compliant email messages. Future plans would be to expand the messages with more complex EAI examples (and/or UTF-8 data in general, e.g. UTF-8 subjects) and "troublesome" messages that pop up during testing. Messages are currently stored here: https://github.com/slusarz/uasg-eai[github.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_slusarz_uasg-2Deai&d=DwMCaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=YI0XKyKCabKQi3GVWLvuoyCWjH9WBgEBxLbMnmhSRwo&m=MaA54taFNGS0KiOaaNK5XMVUigFoeLpSy307iPcGKds&s=XMrCzaDag3RazBLeJF9xpVWtLBzs_pKOlbJRsypWZZE&e=> Corrections to the example messages are encouraged. I transferred the addresses from UASG004 but have not had the ability to test out parsing/reading the messages with EAI-compliant mail tools. Additional message examples are obviously also welcome. -- kind regards, Michael Slusarz Senior Sales Engineer Phone: +1 (303) 888-1090 Skype: michael.m.slusarz Email: michael.slusarz@open-xchange.com<mailto:michael.slusarz@open-xchange.com> Twitter: @openexchange[twitter.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_openexchange...> - Facebook: OpenXchange[facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_OpenXc...> - Web: www.open-xchange.com[open-xchange.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.open-2Dxchange.com&d...> [cid:image010.png@01D3A6A2.40C32540] Open-Xchange AG, Rollnerstr. 14, 90408 Nuremberg, District Court Nuremberg HRB 24738 Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Uwe Reumuth Chairman of the Board: Richard Seibt European Office: Open-Xchange GmbH, Olper Huette 5f, D-57462 Olpe, Germany, District Court Siegen, HRB 8718 Managing Directors: Frank Hoberg, Martin Kauss US Office: Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential, and may be privileged. If you are not the intended recipient, you are hereby notified that any review, retransmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, and delete this message and any attachments from your system.

On February 14, 2018 at 1:10 PM Don Hollander <don.hollander@icann.org> wrote:

Do you (ie OpenXchange) or someone else within the EAI group have a set of tests that should be run and the expected results?

For example:

From ascii@idn.idn                To ascii@ascii.ascii hosted by an EAI Ready mail system                To ascii@ascii.ascii hosted by a non-EAI ready mail system

Expected results:                Name displays properly                Something else?

Neither I (nor my employer) has a test suite that incorporates EAI testing specifically. A general purpose test methodology may be difficult to establish in practice. E.g. something like an LMTP server may not need to test much around EAI specifically at all - it's more of a general exercise in accepting UTF-8 characters where they may have been forbidden previously and/or parsing an EAI address into mailbox and domain components, but may have no desire in verifying those parts. So a "successful" test for this software may look much different than a "successful" test for client software that is creating RFC complaint mail messages interacting with an SMTP relay. And that SMTP server will have different (+ more numerous and broad) tests. I think the approach of 1) providing examples of well-formed messages and 2) documentation/guidelines on how the system is expected to work end-to-end is the correct path. However, I worry that pushing a specific testing agenda or procedure is not proper; we can give tools to help spur testing, but ultimately it is the software author(s) responsibility to adapt the available tools into their product. michael