MailChimp - Is it EAI Ready?
Today I received a message in my toa@ngāpukapuka.nz mailbox from a sender through MailChimp! That seems to show that it is at least Phase 1 EAI Ready. I now also have a unicode@idn.nz <mailto:unicode@idn.nz> address (kōrero@ngāpukapuka.nz) and will start experimenting with that. Don
toa@xn--ngpukapuka-vfb.nz writes:
Today I received a message in my toa@ngāpukapuka.nz mailbox from a sender through MailChimp!
IIRC at least four other companies in the same sector are too, namely Elastic Email, Mailgun, Return Path and SMTP2Go. (Some of those would disagree that they are in the same sector — there's email and email.) JFYI, the message you sent isn't an EAI message, it's a legacy message that happened to use "xn--" in the domain. If you look at the Received fields, you can see it was transmitted by the initial sender via "smtp", not one of the protocol types specified in RFC 6531 section 4.3. For this reason, the top line of this message is actually an accurate rendering of the address according to your instructions (which I expect do not match your intention). Arnt
Thanks Arnt. And yes, I do recognise that. Now that I have an easy to use (for me) unicode@idn.nz address, I'll be trying it more. But you raise the question that we'll be addressing soon - what are our criteria for evaluation of EAI Readines! D -----Original Message----- From: UA-EAI <ua-eai-bounces@icann.org> On Behalf Of Arnt Gulbrandsen Sent: Wednesday, 28 March 2018 10:50 PM To: ua-eai@icann.org Subject: Re: [UA-EAI] MailChimp - Is it EAI Ready? toa@xn--ngpukapuka-vfb.nz writes:
Today I received a message in my toa@ngāpukapuka.nz mailbox from a sender through MailChimp!
IIRC at least four other companies in the same sector are too, namely Elastic Email, Mailgun, Return Path and SMTP2Go. (Some of those would disagree that they are in the same sector — there's email and email.) JFYI, the message you sent isn't an EAI message, it's a legacy message that happened to use "xn--" in the domain. If you look at the Received fields, you can see it was transmitted by the initial sender via "smtp", not one of the protocol types specified in RFC 6531 section 4.3. For this reason, the top line of this message is actually an accurate rendering of the address according to your instructions (which I expect do not match your intention). Arnt _______________________________________________ UA-EAI mailing list UA-EAI@icann.org https://mm.icann.org/mailman/listinfo/ua-eai
participants (3)
-
Arnt Gulbrandsen -
Don Hollander -
toa＠xn--ngpukapuka-vfb.nz