<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)"> <style></style> </head> <body lang="EN-US" link="#0563C1" vlink="#954F72"> <div class="WordSection1"> The most important thing for me is I don’t know how to type those letters on my English keyboard ☹<o:p></o:p> <o:p> </o:p> But yes I agree, forcing Latin chars is the best way to solve this problem.<o:p></o:p> <o:p> </o:p> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"> From: Michele Neylon - Blacknight <michele@blacknight.com> Sent: Tuesday, November 19, 2019 3:21 PM To: David Guo <david@xtom.com>; Thomas Hungenberg <th@cert-bund.de>; anti-abuse-wg@ripe.net Subject: Re: [anti-abuse-wg] Non-ASCII characters in abuse-mailbox addresses<o:p></o:p> </div> </div> <o:p> </o:p> Why?<o:p></o:p> <o:p> </o:p> It’s an EAI issue more than anything else.<o:p></o:p> <o:p> </o:p> If your email client or server can’t handle UTF-8 then doing the punycode conversion is unlikely to help<o:p></o:p> <o:p> </o:p> I’d also encourage RIPE NOT to force Latin characters only – the RIPE region covers multiple languages which are not Latin based and if anything it should be leading by example<o:p></o:p> <o:p> </o:p> More details on EAI and UA issues here:<o:p></o:p> <a href="https://uasg.tech/">https://uasg.tech/</a><o:p></o:p> Regards<o:p></o:p> <o:p> </o:p> Michele<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <div> --<o:p></o:p> Mr Michele Neylon<o:p></o:p> Blacknight Solutions<o:p></o:p> Hosting, Colocation & Domains<o:p></o:p> <a href="https://www.blacknight.com/">https://www.blacknight.com/</a><o:p></o:p> <a href="https://blacknight.blog/">https://blacknight.blog/</a><o:p></o:p> Intl. +353 (0) 59 9183072<o:p></o:p> Direct Dial: +353 (0)59 9183090<o:p></o:p> Personal blog: <a href="https://michele.blog/"> https://michele.blog/</a><o:p></o:p> Some thoughts: <a href="https://ceo.hosting/"> https://ceo.hosting/</a> <o:p></o:p> -------------------------------<o:p></o:p> Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty<o:p></o:p> </div> Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845<o:p></o:p> <o:p> </o:p> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"> From: anti-abuse-wg <<a href="mailto:anti-abuse-wg-bounces@ripe.net">anti-abuse-wg-bounces@ripe.net</a>> on behalf of David Guo via anti-abuse-wg <<a href="mailto:anti-abuse-wg@ripe.net">anti-abuse-wg@ripe.net</a>> Reply to: David Guo <<a href="mailto:david@xtom.com">david@xtom.com</a>> Date: Tuesday 19 November 2019 at 13:34 To: Thomas Hungenberg <<a href="mailto:th@cert-bund.de">th@cert-bund.de</a>>, "<a href="mailto:anti-abuse-wg@ripe.net">anti-abuse-wg@ripe.net</a>" <<a href="mailto:anti-abuse-wg@ripe.net">anti-abuse-wg@ripe.net</a>> Subject: Re: [anti-abuse-wg] Non-ASCII characters in abuse-mailbox addresses<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> <div> <div> Oh you already tried and it works. I suggest RIPE can convert the IDN domains to punnycode on database.<o:p></o:p> </div> </div> <div> <o:p> </o:p> </div> </div> <div class="MsoNormal" align="center" style="text-align:center"> <hr size="2" width="98%" align="center"> </div> <div id="divRplyFwdMsg"> From: David Guo <<a href="mailto:david@xtom.com">david@xtom.com</a>> Sent: Tuesday, November 19, 2019 2:32:54 PM To: Thomas Hungenberg <<a href="mailto:th@cert-bund.de">th@cert-bund.de</a>>; <a href="mailto:anti-abuse-wg@ripe.net">anti-abuse-wg@ripe.net</a> <<a href="mailto:anti-abuse-wg@ripe.net">anti-abuse-wg@ripe.net</a>> Subject: Re: [anti-abuse-wg] Non-ASCII characters in abuse-mailbox addresses <o:p></o:p> <div> <o:p></o:p> </div> </div> <div> <div> <div> <div> Did you try IDN / Punnycode converter?<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> Try <a href="mailto:abuse@xn--zrich-kva.email"> abuse@xn--zrich-kva.email</a> ?<o:p></o:p> </div> </div> <div> <o:p> </o:p> </div> </div> <div class="MsoNormal" align="center" style="text-align:center"> <hr size="1" width="100%" align="center"> </div> <div id="x_divRplyFwdMsg"> From: anti-abuse-wg <<a href="mailto:anti-abuse-wg-bounces@ripe.net">anti-abuse-wg-bounces@ripe.net</a>> on behalf of Thomas Hungenberg <<a href="mailto:th@cert-bund.de">th@cert-bund.de</a>> Sent: Tuesday, November 19, 2019 2:27:13 PM To: <a href="mailto:anti-abuse-wg@ripe.net">anti-abuse-wg@ripe.net</a> <<a href="mailto:anti-abuse-wg@ripe.net">anti-abuse-wg@ripe.net</a>> Subject: [anti-abuse-wg] Non-ASCII characters in abuse-mailbox addresses <o:p></o:p> <div> <o:p></o:p> </div> </div> <div> <div> Hi, some abuse contacts registered with RIPE use non-ascii characters with the abuse-mailbox addresses, e.g. % Abuse contact for '195.78.76.0 - 195.78.77.255' is 'abuse@zürich.email' However, the corresponding MTA does not support SMTPUTF8: 7B579403C6: to=<<a href="mailto:abuse@zürich.email">abuse@zürich.email</a>>, relay=mail.xn--zrich-kva.email[109.95.241.50]:25, delay=0.33, delays=0.01/0/0.32/0, dsn=5.6.7, status=bounced (SMTPUTF8 is required, but was not offered by host mail.xn--zrich-kva.email[109.95.241.50]) (In this particular case, sending email to the IDNA representation of the email address <<a href="mailto:abuse@xn--zrich-kva.email">abuse@xn--zrich-kva.email</a>> works.) In our experience, using umlauts and other non-ascii characters in (the host part of) email addresses still cause a lot of problems in general. Even if the recipient's MX supports SMTPUTF8 correctly, MTAs on the transport way may fail to handle SMTPUTF8 messages. To prevent such problems and make sure all abuse mailboxes can be addressed, I wonder if the values of abuse-mailbox attributes should be restricted to ASCII characters only. What do you think? - Thomas<o:p></o:p> </div> </div> </div> </div> </body> </html>