 |
 |
 |
 |
|
 |
|
 |
|
 |
|
 |
|
|
|
|
|
|
|
|
|
|
|
|
YAO Jiankang wrote:
EAI users should never see the ACE names. They will appear only in downgraded messages and delivered to users who are not using EAI, since EAI -> downgrade -> delivery to EAI client is typically a configuration error. In any case, up-conversion on the receiving side (POP, IMAP, MUA) can apply the reverse translation and restore UTF8 addresses from the ACE encodings.I think receiving a lot of email with long unrecognizable ACE conversions might be incentive for people to upgrade to EAI.it also might be incentive for people to refuse the use of EAI.
As more and more people use EAI, non-EAI users will receive more and more downgraded messages with puunycode addresses. This will build momentum for conversion to the new standard.
The design of punycode ensures that there are no collisions, where more than one UTF8 name maps to the same punycode. As long as all email systems use the same standard ACE that has this property, there will be no collisions when using it.Email administrators can avoid local name collisions as outlined above. This assumption is also important to EAI to avoid collusions on the domain name.you can avoid the name collisions when creating the account, but you can not prohibit the possible name collisions when using it. many MUA and servers may mis-use it since many many MUA or servers might use the automatic one if there is a automatic algorithm.
-Ernie