We are an ESP and we have a lot of customers who send with characters like ü or á, usually in the local part but occasionally in the domain. I think if we converted all from addresses to pure ascii punycode, we'd solve our problems rather than trying to keep them unicode and rely on SMTPUTF8 working. I see Yahoo does not even offer SMTPUTF8
Thanks, Alex -- Alexander Burch ActiveCampaign / Senior Deliverability Engineer abu...@activecampaign.com 1 North Dearborn St Suite 500, Chicago IL, 60602 <https://www.facebook.com/activecampaign> <http://www.twitter.com/activecampaign> <https://www.linkedin.com/company/activecampaign-inc-> <https://plus.google.com/107063868317743606466> <https://www.activecampaign.com/sig/?u=aburch&c=1> On Fri, Mar 3, 2023 at 9:32 AM John R Levine <jo...@taugh.com> wrote: > > Thanks everyone. Is there any reason not to just always use punycode for > > the domain and keep it pure ascii? Seems safer that way. Are there any > > known risks to doing that? > > "Always" in what context? The whole point of IDNs and EAI is so that > people who don't speak English can use mail addresses they can read. > > If you mean in your lists of addresses to send to, sure you can use > A-labels (the ones that contain punycode) and it'll work, although if the > local parts have UTF-8 characters, you still have to do SMTPUTF8 so it's > not much of a shortcut. > > Most of the people with EAI addresses are in India, Thailand, and other > parts of south and east Asia. If you don't do a lot of business there, > you don't need to worry about them. > > R's, > John > > > > > About swaks, there is an open MR to add SMTPUTF8 support: > > > https://urldefense.com/v3/__https://github.com/jetmore__;!!JIZ-LZtDGnv5HBqN_A!MykNXx6yo6uaoX3D_3VQ1iI9p1jeUkSw6Rl62hNqBo1YB1pKliY2BMyPv3L5IAND_HKUjZ2XbsMeFi_m$ > > > > If John Jetmore is here, please merge that sucker! > > > > Thanks, > > Alex > > > > > > -- > > > > Alexander Burch > > ActiveCampaign / Senior Deliverability Engineer > > abu...@activecampaign.com > > 1 North Dearborn St Suite 500, Chicago IL, 60602 > > < > https://urldefense.com/v3/__https://www.facebook.com/activecampaign__;!!JIZ-LZtDGnv5HBqN_A!MykNXx6yo6uaoX3D_3VQ1iI9p1jeUkSw6Rl62hNqBo1YB1pKliY2BMyPv3L5IAND_HKUjZ2XbqfZAr-s$ > > > > < > https://urldefense.com/v3/__http://www.twitter.com/activecampaign__;!!JIZ-LZtDGnv5HBqN_A!MykNXx6yo6uaoX3D_3VQ1iI9p1jeUkSw6Rl62hNqBo1YB1pKliY2BMyPv3L5IAND_HKUjZ2Xbna6n5jx$ > > > > < > https://urldefense.com/v3/__https://www.linkedin.com/company/activecampaign-inc-__;!!JIZ-LZtDGnv5HBqN_A!MykNXx6yo6uaoX3D_3VQ1iI9p1jeUkSw6Rl62hNqBo1YB1pKliY2BMyPv3L5IAND_HKUjZ2Xbot0HO8K$ > > > > < > https://urldefense.com/v3/__https://plus.google.com/107063868317743606466__;!!JIZ-LZtDGnv5HBqN_A!MykNXx6yo6uaoX3D_3VQ1iI9p1jeUkSw6Rl62hNqBo1YB1pKliY2BMyPv3L5IAND_HKUjZ2Xbvl4yHSI$ > > > > > > <https://www.activecampaign.com/sig/?u=aburch&c=1> > > > > > > On Thu, Mar 2, 2023 at 6:20 PM John Levine <jo...@taugh.com> wrote: > > > >> It appears that Alex Burch via mailop <abu...@activecampaign.com> said: > >>> -=-=-=-=-=- > >>> -=-=-=-=-=- > >>> > >>> I am using unicode in the From: not the MAIL FROM. Do you have to > specify > >>> it SMTPUTF8 in the MAIL FROM to use it in the From header? I don't see > >>> anything about that here: > >> > https://urldefense.com/v3/__https://www.rfc-editor.org/rfc/rfc6531__;!!JIZ-LZtDGnv5HBqN_A!LLHjvWO9Lj3NLPOW2WO4wfuIRc6jsmEppjd-E6-oOHDWAguRDF1IVTyo6F7qheRN7lfhCKHmFEIrsWFs$ > >> > >> See section 3.6 which refers to an "internationalized message" and RFC > >> 6532 which explains what that means. It roughly means you can have > >> UTF-8 in the headers. > >> > >>> I was under the impression that if the client offered SMTPUTF8 > extension > >>> then you could go ahead and use unicode in the headers like From. > >> > >> You can, but you have to put the SMTPUTF8 parameter on the MAIL FROM to > say > >> it's an internationalized message. > >> > >> I did a bunch of EAI mail tests for ICANN's UASG and Gmail passed most > of > >> them. > >> If you use the correct envelope and headers, it'll work. > >> > >> Someone else asserted that nobody handes Unicode domain names, and he is > >> wrong, > >> although the have to be encoded as A-labels when you do the DNS lookup, > as > >> described in RFCs 5894 and 5895. > >> > >> R's, > >> John > >> > >> > >> > > > > Regards, > John Levine, jo...@taugh.com, Taughannock Networks, Trumansburg NY > Please consider the environment before reading this e-mail. > https://urldefense.com/v3/__https://jl.ly__;!!JIZ-LZtDGnv5HBqN_A!MykNXx6yo6uaoX3D_3VQ1iI9p1jeUkSw6Rl62hNqBo1YB1pKliY2BMyPv3L5IAND_HKUjZ2Xbt5FsPoR$ >
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
