> For example, if a user enters <JPuserid>@<JPdomain.dom> then that should
> be encoded as <iso-2022-jp>@<ACE-encoding> on message SEND, with the
> mailer doing an ACE conversion on the domain part at the same time as it
> does an RFC-2047 conversion on the user part.
no, that would be insane.
1. as already stated, RFC 2047 frequently gets munged by things that
handle mail. this would corrupt the local-part of the address
2. as already stated, there is no canonical form of RFC 2047 encoding -
the same string can be encoded in an arbitrary number of ways. And
SMTP servers aren't equipped to decode RFC 2047 before comparing
a recipient address with a list of valid addresses.
the requirements for local-parts of email addresses are quite similar
to those of domain names. ACE is much closer to this than RFC 2047.
Keith
